Skip to content
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

Open
wants to merge 4 commits into
base: next
Choose a base branch
from

Conversation

illright
Copy link
Member

@illright illright commented Dec 9, 2024

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

@illright illright requested a review from daniilsapa December 9, 2024 18:11
Copy link

changeset-bot bot commented Dec 9, 2024

🦋 Changeset detected

Latest commit: 20b5ecf

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 2 packages
Name Type
@feature-sliced/steiger-plugin Minor
steiger Patch

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.
Copy link
Collaborator

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?

Copy link
Member Author

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

@illright illright changed the base branch from master to next December 9, 2024 20:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants