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
Is your feature request related to a problem? Please describe.
Sometimes in a monorepo we want to declare all packages from the same organization group (e.g.: @mymonorepo/test)
Describe the solution you'd like
I would like a rule that shows me package.jsons whose name starts with a different prefix
Describe alternatives you've considered
I didn't found alternatives other than implementing something manually
Additional context
Maybe this capability could be added to modules-same-contents by manipulating jmespath or something :)
The text was updated successfully, but these errors were encountered:
Great! For me that’s it :)Sent from my iPhoneOn 23 Nov 2022, at 21:37, Sergio Eduardo Flores Jr. ***@***.***> wrote:
I like the idea!
I think it could be a rule on its own also.
{
"modules-same-organization": "@<org_name>"
}
What do you think?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
Is your feature request related to a problem? Please describe.
Sometimes in a monorepo we want to declare all packages from the same organization group (e.g.: @mymonorepo/test)
Describe the solution you'd like
I would like a rule that shows me package.jsons whose name starts with a different prefix
Describe alternatives you've considered
I didn't found alternatives other than implementing something manually
Additional context
Maybe this capability could be added to modules-same-contents by manipulating jmespath or something :)
The text was updated successfully, but these errors were encountered: