fix(no-export-in-script-setup): better report location #2701
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
FloEdelmann changed the title FloEdelmann changed the title 
FloEdelmann requested changes Mar 5, 2025
chouchouji force-pushed the improve-no-export-in-script-setup branch 3 times, most recently from 0aafec6 to bf87c65 Compare chouchouji force-pushed the improve-no-export-in-script-setup branch from bf87c65 to b92dc0a Compare 
FloEdelmann changed the title Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
support autofix for no-export-in-script-setup rule.
relates to #2690