Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
Currently, the
import/prefer-default-export
rule from eslint-plugin-import is being used. This rules enforces a default (versus named) export when only one thing is exported from a module.There are good arguments to use named exports instead of default exports, like the ones explained in this document or in this post.
What has been done
Summary: the prefer default export requirement has been inverted, now all exports must be named.
Commits:
import/prefer-default-export
rule withimport/no-default-export
in the.eslintrc.json
file.In particular you have to check
The rule disabling in the vue component type definition. Maybe I should ignore the rule in a different way, like using overrides in the
.eslintrc.json
file.Additional info (screenshots, links, sources, etc.)