Open JounQin opened 8 months ago
Hi @JounQin . Thanks for your contribution to prettier & eslint ecosystem!
It would be nice for eslint-plugin-prettier to support those features natively. But I think this fork might not be an ideal implementation:
Based on your knowledgement about prettier, I believe that you can find a better way to support similar features. Let me know if I could help anything.
It would be nice for eslint-plugin-prettier to support those features natively. But I think this fork might not be an ideal implementation:
@vue/compiler-sfc
as optional peer dependency, for other frameworks, we use other compiler/parser insteadBased on your knowledgement about prettier, I believe that you can find a better way to support similar features. Let me know if I could help anything.
Thanks, I do have some ideas as described above, I'm thinking what's the best choice or we may be able to support all choices.
The benefit of eslint-plugin-prettier
is that it can be reported by tools like VSCode ESLint plugin, while VSCode prettier won't check the file on editing.
Hi @meteorlxy !
I'm the current active maintainer of https://github.com/prettier/eslint-plugin-prettier, and just see this fork accidentally few days ago.
And I think about that is there any chance to merge this fork back into upstream? I believe that the custom blocks support is great for such frameworks commonly like Vue, Svelte, Astro, etc.
If you agree and want to raise a PR for upstream that'll be appreciated. Otherwise I'll think about how to implement such features in
eslint-plugin-prettier
.I want us to collaborate together with @BPScott.