-
Notifications
You must be signed in to change notification settings - Fork 106
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 report lint issues not on first char of file for .vue
and support ESLint fixes and suggestions
#2735
Conversation
🦋 Changeset detectedLatest commit: 253e17c The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
processorVueBlocks({ | ||
blocks: { | ||
styles: false, | ||
customBlocks: true, |
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.
should I remove processing custom blocks? @bmulholland
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.
I didn't even know you could do that! They sound cool... and like something that should be out of scope for now.
They're custom, so you'd want to pretty careful with the scenario. Best for someone to have the need and share what it is in more detail. That would probably be a very long tail thing though... honestly probably can always ignore.
@@ -2,8 +2,6 @@ | |||
<span>test</span> | |||
</template> | |||
<script> | |||
/* eslint-disable no-unused-vars */ |
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.
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.
Yeah it wouldn't be the first time I see a lint disabling a rule and also disabling the unused-directive check hah.
You could easily just use the variables, though. I'll post code above.
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.
Did that work?
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.
nope, because it's upstream issue from merge-processors antfu/eslint-processor-vue-blocks#8 (comment)
.vue
and support ESLint fixes and suggestions
blocks: { | ||
styles: false, | ||
customBlocks: true, | ||
script: true, |
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.
also what about this scriptSetup
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.
Script setup is essentially the new standard, best practice way to write Vue components. Almost all my code is in that, or migrating to it. Should certainly be supported.
Oh wow this is really exciting! I'll take a look :) |
Nice find on that package! If you think this is ready, I can try it out on my project. I always struggle with trying unpackaged JS libraries (spoiled by Ruby, I suppose). Could I just clone this branch and use |
graphql-eslint needs a new alpha release to try it out, I will do it in few minutes with bug fix you will need just update your project according new vue example |
💻 Website PreviewThe latest changes are available as preview in: https://2277a208.graphql-eslint.pages.dev |
fixes #2103
cc @bmulholland