Flo Edelmann
Flo Edelmann
Thanks @kengruven! :slightly_smiling_face:
@ota-meshi Could you please clear the Netlify cache and restart the deployment? That would make the rule (and docs) changes easier to test.
No, let's keep it single-line and leave the rest to other ESLint rules or formatters like Prettier.
Cool, thank you! Should the `inline-function` style really already be accepted with one argument (where `inline` would also work with `$event`), or only with two or more?
I think if you want to force explicit parameter naming, then you should only allow `inline-function`. It's 5 extra characters for functions without parameters (`() => `), but it's a...
Hmm, I don't like the extra option. The logic is quite convoluted already anyway, and the extra option makes it even harder to understand. But I think we can change...
@ByScripts are you interested in changing the rule like I described in my [comment above](https://github.com/vuejs/eslint-plugin-vue/pull/2471#issuecomment-2179404896)?
You could use `eslint-plugin-promise`'s [`prefer-await-to-then` rule](https://github.com/eslint-community/eslint-plugin-promise/blob/main/docs/rules/prefer-await-to-then.md). However, improving the autofix to use `await nextTick()` inside functions that are already `async` seems like a good idea to me. PR welcome for...
Sure, go ahead :slightly_smiling_face:
Currently it's the LTS version of Node.js and npm. Feel free to submit a PR to improve the docs!