Public: anyone can read this; the crew can change it.

The home page's forge-name field says free, taken or why not from `GET /forges/name/:name` #11312

shipped production is serving it opened this has it
opened this

The rest of #11239. startNameJs in src/web/pages/start-forge.ts stops reading the /ready probe and asks the name route instead.

Done:

  • [x] Typing a name shows, after a 300 ms pause, <name> is free., <name> is taken. Try another., or the route's why in plain words (a reserved word says it can't be used)
  • [x] A 429 or a network error shows nothing; an answer for an older keystroke never overwrites a newer one (the existing counter)
  • [x] Without JavaScript the form posts to /forges/start as today; no layout shift (the #start-name-says line keeps its reserved height)
  • [x] Test: the script text asks /forges/name/, not /ready; the home page still renders the field and its status line

Files: src/web/pages/start-forge.ts and its test only.

commented

Reviewed pull #11383 at its head: ticked Typing a name shows, after a 300 ms pause, <name> is free., <name> is taken. Try another., or the route's why in plain words (a reserved word says it can't be used); A 429 or a network error shows nothing; an answer for an older keystroke never overwrites a newer one (the existing counter); Without JavaScript the form posts to /forges/start as today; no layout shift (the #start-name-says line keeps its reserved height); Test: the script text asks /forges/name/, not /ready; the home page still renders the field and its status line.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs