-
Notifications
You must be signed in to change notification settings - Fork 334
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
Assert Exit this page HTMLAnchorElement
button and clearly guard all dynamic fields
#4321
Conversation
📋 StatsFile sizes
Modules
View stats and visualisations on the review app Action run for 8d85f0a |
7831fd9
to
53693b3
Compare
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.
Looks good to me, though I've had to get my head out of the Error messages space to allow it to accept early returns again 😆
Could we sneak in a coupla words to cover the guards in the PR title? Or give it a more general message about tightening up checks?
HTMLAnchorElement
buttonHTMLAnchorElement
button and clearly show optional fields
53693b3
to
8d85f0a
Compare
HTMLAnchorElement
button and clearly show optional fieldsHTMLAnchorElement
button and clearly guard all dynamic fields
@domoscargin Thanks for reviewing, all updated and rebased |
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 PR is a follow up to #4129 (see #4199) to fix the "link button" check:
We should catch this early to ensure
location.href
changes work correctlyI've also added some extra guards for dynamic elements so it's clear which ones we chose to throw errors for