-
-
Notifications
You must be signed in to change notification settings - Fork 669
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
feat: implement require-explicit-slots #2325
feat: implement require-explicit-slots #2325
Conversation
Looks like the tests are failing 🤔 They all pass locally, let me see if there is some version mismatch somewhere. EDIT: Seems to be due to node version. It fails on 14 but succeeds on 16. I'm thinking:
Maybe this is ok? I'm not sure what the protocol is for these cases so I'll wait for the reviewers' input 🙇 |
We plan to drop support for Node v14 and v16 in eslint-plugin-vue v10 (see #2166), so new rules intended to be merged before that major version should be compatible with Node v14 as well. But we can also mark this PR as a breaking change and only release it with or after v10. |
@FloEdelmann I think this makes sense to introduce in v10 then since consumers of it wouldn't be on node 14 anyway due to the reasons mentioned above 🙏 |
@ota-meshi @FloEdelmann I made some changes to the implementation based on the comments. Could you please take another look when you get the chance? 🙏 |
@ota-meshi I addressed the comments. I'm not sure if I understood the comment about the docs correctly. I'll make the change if it's still wrong |
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.
LGTM! Thank you!
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.
Thanks for implementing the feedback! This looks good to me now 🙂
This is an attempt at solving #2294
I would like to hear your opinion on the handling of slots declared twice. As you can see from the implementation, I'm reporting this as well but I'm not sure if such a thing should be responsibility of this rule.
What do you think?
Also, I did not implement a fixer for now as we do not know how the slot function is typed. I think this is good enough for now but any opinions?
Thank you.