eslint: Add vue setup compiler macros#173
Conversation
|
Hey there! Do you have the time to add a prompt question asking "do you plan to use <script setup>?" or similar (with an appropriate link) and enable those rules just for who accept it? |
|
Hi, so I've figured, the setting in this PR only works when upgrading Is this feasible for the starter kit? If yes I can also do the work of checking with a fresh start kit what is needed for other script setup things. |
|
I think half of the ecosystem is waiting for We could just do the upgrade for some ESLint presets, but it would be hard to maintain, that's why we are waiting to do the switch |
|
I see... works fine for me, but I see there are still issues so this PR will have to wait 💁♂️ Added a shy bump to the eslint-plugin-node issue 😋 Thx :) |
|
Thanks to you for caring and proposing a fix :) |
See:
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
devbranch and not themasterbranchfix: #xxx[,#xxx], where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: