-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
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
Add import-locality
to the set of FSD rules
#143
base: next
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 20b5ecf The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
</details> | ||
|
||
### Migration from 0.4.0 | ||
|
||
Version 0.5.0 introduced a new config file format. Follow the [instructions](../../MIGRATION_GUIDE.md) to migrate your config file. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will lead to broken links in packages/steiger/README.md
as we have these documents only on the top level of the repository. Is that ok?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good point. I think there's not a lot we can do about it for now, since this README is published to npm, and there we have no MIGRATION_GUIDE.md file at all, so this link is bound to be broken until we make a documentation site
Addresses #142 (won't close it, we'll close it manually when we release). We forgot to add that rule to the array of all rules