chore: simplify source ownership #16333
Merged
+45
−21
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.
I have a feeling we could make this simpler still, by comparing the
update_version
with the value at the time when the signal was created, but I haven't yet figured out an approach that doesn't result in an additional property on the signal (I thought we could userv
, but it makes it harder to avoid duplicate dependencies).In the meantime, we don't need to create an object with a
reaction
property in addition to the sources; as long as we updatesource_ownership
(here renamed tocurrent_sources
) when we need to lazily create sources insideproxy.js
. Previously we were usingset_active_reaction
as a way to achieve the same outcome, but in a more roundabout way (normally that function is used so that the effect tree is constructed correctly, but that doesn't apply here).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 test
and lint the project withpnpm lint