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
the option "import-locality" described in the documentation is not exist in the package
The text was updated successfully, but these errors were encountered:
Perhaps it's because you need to add fsd/ before the rule name? Sorry for the confusion, we should update the readme
fsd/
Sorry, something went wrong.
i tried this
Invalid configuration in steiger.config.js: Required at "[2].ignores", or Invalid enum value. Expected 'fsd/ambiguous-slice-names' | 'fsd/excessive-slicing' | 'fsd/forbidden-imports' | 'fsd/inconsisten t-naming' | 'fsd/insignificant-slice' | 'fsd/no-layer-public-api' | 'fsd/no-public-api-sidestep' | 'fsd/no-reserved-folder-names' | 'fsd/no-segmentless-slices' | 'fsd/no-segments-on-sliced-layers' | 'f sd/no-ui-in-app' | 'fsd/public-api' | 'fsd/repetitive-naming' | 'fsd/segments-by-purpose' | 'fsd/shared-lib-grouping' | 'fsd/typo-in-layer-name' | 'fsd/no-processes', received 'fsd/import-locality' at "[2].rules.fsd/import-locality", or Required at "[2].meta"; Required at "[2].ruleDefinitions"
Ah, sorry, I see what the problem is now. We forgot to include that rule in the ruleset. We'll add it in the next release, thanks for noticing!
import-locality
No branches or pull requests
the option "import-locality" described in the documentation is not exist in the package
The text was updated successfully, but these errors were encountered: