feat: allow use of createContext when instantiating components programmatically #17575
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This enables an advanced pattern when creating type-safe context with
createContext— you can pass a wrapper component tomountorhydrateorrenderthat calls the setter before calling the component. The only reason this was previously impossible was because a component context wasn't automatically created for the root, unlesscontextwas provided.It seems likely that we'll want to deprecate
setContext,getContext,hasContextand thecontextoption in the future, sincecreateContextis a superior approach. This PR doesn't do anything in that direction though — we can consider that separately.Alternative to #17515, closes #16997.
Before submitting the PR, please make sure you do the following
feat:,fix:,chore:, ordocs:.packages/svelte/src, add a changeset (npx changeset).Tests and linting
pnpm testand lint the project withpnpm lint