solidjs / solid / 39630427932

78%

main: 89%

push

github

fix(signals,solid): explain undefined context values in the dev ContextNotFoundError (#4181) (#4201)

`undefined` keeps meaning "not provided" for context, but the old message
("must either be created with a default value...") read as wrong when the
caller had passed `createContext(undefined)` or a provider had passed
`value={undefined}`. In dev the error now names the context and says which
case it hit (no provider and no default, an explicit undefined default, or a
provider passing undefined), and suggests `null` as the explicit empty
value. Client and server read paths both pass the context in dev only;
production messages and bundles are unchanged.

Docs (RFC 02, MIGRATION, CHEATSHEET, createContext JSDoc) now state that
undefined is "not provided" and that null makes a context optional.


Claude-Session: https://claude.ai/code/session_015hPxMkC3jg3Uivh65gvaf2

Co-authored-by: Claude <noreply@anthropic.com>

762 of 1055 branches covered (72.23%)

Branch coverage included in aggregate %.

2 of 2 new or added lines in 1 file covered. (100.0%)

1105 of 1349 relevant lines covered (81.91%)

27.52 hits per line