fix(runtime): prevent watchers from prematurely firing in custom elements build#2971
Merged
rwaskiewicz merged 3 commits intomasterfrom Jul 21, 2021
Merged
Conversation
…ent build - wait for a component to be defined in the CustomElementsRegistry before setting the isWatchReady flag
ltm
approved these changes
Jul 21, 2021
rwaskiewicz
added a commit
that referenced
this pull request
Aug 17, 2021
…ents build (#2971) - wait for a component to be defined in the CustomElementsRegistry before setting the isWatchReady flag
2 tasks
This file contains hidden or 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
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.
Pull request checklist
Please check if your PR fulfills the following requirements:
npm run build) was run locally and any changes were pushednpm run test.karma.prod) was run locally and passedPull request type
Please check the type of change your PR introduces:
What is the current behavior?
When using the custom elements build, it's possible that
@Watchannotated methods will fire before our components are fully instantiated. This is inconsistent with the lazy load build, as well as the Stencil documentation:GitHub Issue Number: N/A
What is the new behavior?
@Watchmethod can be firedDoes this introduce a breaking change?
However, folks that are using the custom elements build may see watchers not firing as they expect. So we should either
v3.0.0-devinsteadTesting
Programmatic tests have been pushed to a future story, as the work required to get that wired up is beyond the scope of this effort
Manual:
Replication
npm cinpm start)npm serve)What's happening?
For the custom element build,
runTestis being invoked when the component is ready according to theCustomElementRegistry, not according to Stencil. Stencil hasn't finished building the component on its side, but the@Watchis fired.Testing the Fix
npm ci && npm run build && npm packnpm i <PATH_TO_STENCIL>/stencil-core-2.7.0-0.tgznpm start)npm serve)Other information