Post

Sometimes when you're naming a flag, nothing seems to stick. You try for weeks, ask everyone you know, but the "right" name doesn't seem to be there. Eventually maybe you just ship a name that's bad enough that you figure people will read the docs to figure out what it does.

24/4/26, 11:18 pm2 reposts15 likes

Ryan "UnionToTuple" Cavanaugh

@searyanc.dev

24 Apr

Years later you'll wonder "Was there a better name for this? Will someone else find what was hiding right under our eyes?" Anyway, TIL that flow also chose to call it noUncheckedIndexedAccess

John Reilly

@johnnyreilly.com

25 Apr

I remember the poll for this!!

Yoz Grahame

@yoz.bsky.social

25 Apr

argh I hate negatives in flag names, they usually make things more confusing Though I like the idea of “make it confusing enough that people HAVE to go look it up”

Remco Haszing

@remcohaszing.nl

25 Apr

It’s especially bad for CLI flags, because I expect `--no-foo` to set `foo` to false.

Mark Erikson

@acemarke.dev

25 Apr

Hello, I'm the person responsible for Redux Toolkit's `extraReducers` field in the `createSlice` API. It's stupid. I'm sorry :) But I had no better ideas at the time, we needed to ship 1.0, and it went live and we're stuck with it :) (and despite complaints no one ever gave a better name...)