-
-
Notifications
You must be signed in to change notification settings - Fork 629
refactor(linter): introduce ContextSubHost
for cross script block analyse
#12724
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
base: main
Are you sure you want to change the base?
refactor(linter): introduce ContextSubHost
for cross script block analyse
#12724
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. |
CodSpeed Instrumentation Performance ReportMerging #12724 will not alter performanceComparing Summary
|
bf94758
to
23e3b37
Compare
23e3b37
to
646cd76
Compare
f72c007
to
5f79f25
Compare
5f79f25
to
81fac36
Compare
Another approach to #12541 stack.
Because
vue/valid-define-emit
and other rules required the semantics of the other script block.The Goal:
Linter.run
should run with the complete file context. Invue
files and others, there can be multiple Semantics / Module Records.Because
vue
requires some magic compiler rules, the linter should have access to the complete file.This will also fix the offset bug in #12758.
Don't merge both stacks without rebasing.I do not like the loop part. Maybe you guys have some better ideas.