You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The base config we use sets 'import/first': ['error', 'absolute-first'],
However, while we want the imports to be at the top, we don't need them to be sorted beyond that. As such, we don't need 'absolute-first' set.
Before, we redefined the rule through "import/first": ["error", ""],
However, since 2.20.1 the config only allows 'absolute-first' string in options. Since there is only one option to redefine, and severity changes don't override options, it is impossible to unset 'absolute-first' from derived config right now.
This seems like unintended behavior.
Could you perhaps add an option to explicitly turn off absolute-first?
The text was updated successfully, but these errors were encountered:
TheCrueltySage
changed the title
[import/first] Impossible to turn off absolute-import from base config
[import/first] Impossible to turn off absolute-import from dervied config
Feb 18, 2020
The base config we use sets
'import/first': ['error', 'absolute-first'],
However, while we want the imports to be at the top, we don't need them to be sorted beyond that. As such, we don't need 'absolute-first' set.
Before, we redefined the rule through
"import/first": ["error", ""],
However, since 2.20.1 the config only allows 'absolute-first' string in options. Since there is only one option to redefine, and severity changes don't override options, it is impossible to unset 'absolute-first' from derived config right now.
This seems like unintended behavior.
Could you perhaps add an option to explicitly turn off absolute-first?
The text was updated successfully, but these errors were encountered: