-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow reloadExtension() to soft fail #29042
Allow reloadExtension() to soft fail #29042
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we also add a protection against evaluating a second script of the same extension?
src/service/extensions-impl.js
Outdated
); | ||
if (!els.length) { | ||
const TAG = 'reloadExtension'; | ||
user().warn( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's make this an error
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's already a different error for this: Error: amp-fit-text is already registered. The script tag for amp-fit-text is likely included twice in the page.
Happens in custom-element-registry.js when we try to register a CE twice.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That happens too late, though, since any side-effects in the code can already execute. I think we need an earlier check in runtime.js
when we're processing the pushed ExtensionPayload
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right and it doesn't cover non-CE extensions. I guess we have a similar check for templates. #29050
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This got off topic from the request. Let's make this an error, not a warn.
We can solve the escape hatch in a follow up.
Fixes #28582 and
b/158855528
.