-
Notifications
You must be signed in to change notification settings - Fork 2k
feat(boundaries): implicit dependencies #10117
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
My only concert is the possibility of using implicitDependencies
to cover up a bad package graph.
pub tags: Option<Spanned<RulesMap>>, | ||
pub implicit_dependencies: Option<Spanned<Vec<Spanned<String>>>>, |
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.
Just noticed in the snapshots we're serializing "implicitDependencies": null
, maybe #[serde(skip_serializing_if = "Option::is_none")]
?
Description
Allow users to allowlist implicit dependencies for boundaries. This is useful in cases where testing libraries or frameworks can inject globals such as
server-only
Can be reviewed commit by commit
Testing Instructions
Added test to boundaries. Note the snapshots do not change since no errors are produced. To verify stuff is working as intended, try removing the
implicitDependencies
key and note that an error is produced.