-
-
Notifications
You must be signed in to change notification settings - Fork 681
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
Force defineExpose at the end of <script> #2235
Comments
I think it could even be part of |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
I agree and would welcome |
@FloEdelmann @Thomasan1999 @J-Michalek I can give this a try. It differs from the original
|
Please describe what the rule should do:
The rule would force to have
defineExpose
at the end of the<script>
tag. When<script setup>
is used,defineExpose
is used as the alternative toreturn
and is often expected to be at the end the same wayreturn
was. It also uses the data used in<script>
and should therefore not be placed before the data itself. It is similar tovue/define-macros-order
where define macros are forced at the beginning of<script>
.What category should the rule belong to?
[X] Enforces code style (layout)
[ ] Warns about a potential error (problem)
[ ] Suggests an alternate way of doing something (suggestion)
[ ] Other (please specify:)
Provide 2-3 code examples that this rule should warn about:
Additional context
The text was updated successfully, but these errors were encountered: