We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Unnamed functions make certain types of debugging harder (like profiling). It would be nice to avoid them.
This rule looks like it will enforce named arrow functions: https://github.com/getify/eslint-plugin-proper-arrows
This looks like it will enforced named function functions: https://eslint.org/docs/rules/func-names
I haven't tested either one.
The text was updated successfully, but these errors were encountered:
We will probably want to make some exceptions for things like test definitions: describe(__filename, () => {...})
describe(__filename, () => {...})
Sorry, something went wrong.
No branches or pull requests
Unnamed functions make certain types of debugging harder (like profiling). It would be nice to avoid them.
This rule looks like it will enforce named arrow functions: https://github.com/getify/eslint-plugin-proper-arrows
This looks like it will enforced named function functions: https://eslint.org/docs/rules/func-names
I haven't tested either one.
The text was updated successfully, but these errors were encountered: