Change onMount/afterUpdate order #3150
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ings * master: (66 commits) -> v3.4.3 always add raw property to text nodes flesh out in/out transition tutorial chapter (#2792) code style fix test fix tests Fix CRUD example to allow changing input values. Fixes #2714 treat requestAnimationFrame as a noop on the server site: actions tutorial: destroy is not required (#2776) Allow binding of <details> open site: add /faq redirect to GitHub wiki FAQ fix case sensitive import name, improve tsconfig type declarations for bundled files convert everything to TypeScript check for unknown props when creating component cleanup, improve comments typecheck npm script workarond for estree-walker related typings conflict compile/render-dom and other remaining typings ...
…ings * master: (35 commits) Fix overwrite of 'offset' value in reactive statement fix slide example typos update svelte-repl (fixes download button) update svelte-repl update svelte-repl version use better eliza package gitignore workers add compiler typings to list of published files improve typings for animate, easing, transition, motion and internal apis update bundler worker fix gitignore fix types for easing functions fix build order generate internal-exports file update gitignore update folder structure - #2790 bump estree-walker to fix some svelte.walk bugs bundle locally -> v3.4.4 ...
…s://github.com/colincasey/svelte into colincasey-onmount_triggers_in_reverse_order_for_siblings
|
I vote bugfix. This new behavior does make more sense, and there's nothing in the docs that indicates what order this stuff happens, right? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 is an extension of @colincasey's work in #2752. The more I think about it, the more it seems that
onMountshould happen before the firstafterUpdate, since it's likely to be used for setup work (likectx = canvas.getContext('2d')or whatever).The question, of course, is whether that qualifies as a breaking change or a bugfix?
Otherwise it's mostly the same — child
onMount/afterUpdatehappens before parents, and siblings fire their functions in the natural order. I changed the.reverse()and the.shift(), as it's better to avoid that work if possible.