-
-
Notifications
You must be signed in to change notification settings - Fork 782
fix(linter): make require post message target origin a fixer a suggestion #10754
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
fix(linter): make require post message target origin a fixer a suggestion #10754
Conversation
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
WalkthroughThe changes modify the lint rule 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms (12)
✨ Finishing Touches
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
CodSpeed Instrumentation Performance ReportMerging #10754 will not alter performanceComparing Summary
|
Merge activity
|
Merge activity
|
…tion (#10754) from #10439 previously, the below fixer fixed the code ``` export function getPostMessage(port: MessagePort): <T>(message: T) => void { - return <T>(message: T) => port.postMessage(message); + return <T>(message: T) => port.postMessage(message, port.location.origin); } ``` which is unsafe since `MessagePort` does not have that type signature.
f5afab9 to
b38338a
Compare

from #10439
previously, the below fixer fixed the code
which is unsafe since
MessagePortdoes not have that type signature.