philschmid

Begin by enclosing all thoughts within <thinking> tags, exploring multiple angles and approaches.
Break down the solution into clear steps within <step> tags. Start with a 20-step budget, requesting more for complex problems if needed.
Use <count> tags after each step to show the remaining budget. Stop when reaching 0.
Continuously adjust your reasoning based on intermediate results and reflections, adapting your strategy as you progress.
Regularly evaluate progress using <reflection> tags. Be critical and honest about your reasoning process.
Assign a quality score between 0.0 and 1.0 using <reward> tags after each reflection. Use this to guide your approach:

0.8+: Continue current approach
0.5-0.7: Consider minor adjustments
Below 0.5: Seriously consider backtracking and trying a different approach

jtrv

{
    "input": {
        "blocklist": [],
        "compressor#0": {
            "attack": 15.0,
            "boost-amount": 0.0,
            "boost-threshold": -72.0,
            "bypass": false,
            "dry": -80.01,
            "hpf-frequency": 10.0,

Nezteb

Update 2

As of August 28th, 2025, Expert LSP has been released: https://github.com/elixir-lang/expert

Although still a work in progress, the plan is for the other three LS implementations to be archived. I may try to come up with a new way to track Expert's featureset, but I would probably contribute that back to Expert as documentation.

Update

As of August 15, 2024, it's been announced that the three projects bein compared here will soon merge! See the official Elixir blog post for more details: https://elixir-lang.org/blog/2024/08/15/welcome-elixir-language-server-team/

rphlmr

// Credits to Louistiti from Drizzle Discord: https://discord.com/channels/1043890932593987624/1130802621750448160/1143083373535973406

import { sql } from "drizzle-orm";

const clearDb = async (): Promise<void> => {
  const query = sql<string>`SELECT table_name
      FROM information_schema.tables
      WHERE table_schema = 'public'
        AND table_type = 'BASE TABLE';
    `;

rphlmr

// Thanks https://github.com/colinhacks/zod/issues/372#issuecomment-830094773

type Implements<Model> = {
  [key in keyof Model]-?: undefined extends Model[key]
    ? null extends Model[key]
      ? z.ZodNullableType<z.ZodOptionalType<z.ZodType<Model[key]>>>
      : z.ZodOptionalType<z.ZodType<Model[key]>>
    : null extends Model[key]
    ? z.ZodNullableType<z.ZodType<Model[key]>>
    : z.ZodType<Model[key]>;

bholtbholt

// $list has a nested structure like:
// lists: [
//   {
//     "id": "TODO-ns88qrJDVXizlF0l",
//      …properties omitted for brevity
//     "cards": [
//       {
//         "id": "6OPzS6B6WoBT0J_EGqUEy",
//         "listId": "TODO-ns88qrJDVXizlF0l",
//          …properties omitted for brevity

MeetMartin

// JavaScript functional programming
// Monad under 60 seconds

const Functor = {
    of: value => ({
        value: value,
        inspect: () => console.log(`Functor(${value})`),
        map: fn => Functor.of(fn(value))
    })
};

jcreamer898

Type 'from' in the editor and...

qoomon

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

git commit -m"<type>(<optional scope>): <description>" \
  -m"<optional body>" \
  -m"<optional footer>"

jimmywarting

Exposed headers

Service	SSL	status	Response Type	Allowed methods	Allowed headers