Skip to content

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

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

Sysix
Copy link
Member

@Sysix Sysix commented Aug 1, 2025

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. In vue 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.


benchmark results

@github-actions github-actions bot added A-linter Area - Linter C-cleanup Category - technical debt or refactoring. Solution not expected to change behavior labels Aug 1, 2025
Copy link
Member Author

Sysix commented Aug 1, 2025


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • 0-merge - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

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.

Copy link

codspeed-hq bot commented Aug 1, 2025

CodSpeed Instrumentation Performance Report

Merging #12724 will not alter performance

Comparing 08-01-refactor_linter_introduce_contextsubhost_for_cross_script_block_analyse (81fac36) with main (784796d)

Summary

✅ 34 untouched benchmarks

@Sysix Sysix force-pushed the 08-01-refactor_linter_introduce_contextsubhost_for_cross_script_block_analyse branch from bf94758 to 23e3b37 Compare August 2, 2025 16:34
@Sysix Sysix force-pushed the 08-01-refactor_linter_introduce_contextsubhost_for_cross_script_block_analyse branch from 23e3b37 to 646cd76 Compare August 3, 2025 12:38
@Sysix Sysix marked this pull request as ready for review August 3, 2025 15:29
@Sysix Sysix requested a review from camc314 as a code owner August 3, 2025 15:29
@Sysix Sysix force-pushed the 08-01-refactor_linter_introduce_contextsubhost_for_cross_script_block_analyse branch 2 times, most recently from f72c007 to 5f79f25 Compare August 5, 2025 17:59
@Sysix Sysix force-pushed the 08-01-refactor_linter_introduce_contextsubhost_for_cross_script_block_analyse branch from 5f79f25 to 81fac36 Compare August 9, 2025 14:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-linter Area - Linter C-cleanup Category - technical debt or refactoring. Solution not expected to change behavior
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants