You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rationale: Using lifecycle=initialized is useful for isolation. Using lifecycle=render is probably not super useful, since you can always just define a callback. Also, inititalizedCallback inside of lifecycle=initialized doesn't get registered, which makes it not as easy to switch between.
Move the lifecycle= feature to be a recipe, showing how Script can be extended (or just delete)
Add an isolate:=true or context="component" or as="instance" or per-instance:=true or something
Then, change code to still call any exported initializedCallback AFTER calling the function itself during initializedCallback() of Script
The text was updated successfully, but these errors were encountered:
Building on: #22
Rationale: Using
lifecycle=initialized
is useful for isolation. Usinglifecycle=render
is probably not super useful, since you can always just define a callback. Also,inititalizedCallback
inside oflifecycle=initialized
doesn't get registered, which makes it not as easy to switch between.Move the
lifecycle=
feature to be a recipe, showing how Script can be extended (or just delete)Add an
isolate:=true
orcontext="component"
oras="instance"
orper-instance:=true
or somethingThen, change code to still call any exported initializedCallback AFTER calling the function itself during
initializedCallback()
of ScriptThe text was updated successfully, but these errors were encountered: