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

Provide a 'strict_usage' mode that fails the build if deprecated features or anti-patterns are used #151

Open
plaird opened this issue Jun 17, 2022 · 0 comments

Comments

@plaird
Copy link
Contributor

plaird commented Jun 17, 2022

As we collect deprecated attributes, it would be good to allow build teams to eliminate usages of them and prevent new usages. This should be coupled with #78 to configure this mode at the workspace level. It must be False by default to not break back compat.

springboot(
    ...
    strict_usage = True,
)

I can't think of anti-patterns off-hand, but we should leave options open for what could fail the build. We should be clear that there are checks (dupeclass, max dep count, etc) which are not controlled by strict_usage.

@plaird plaird added this to To do in 2.x.x Minor Features and Fixes via automation Jun 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

1 participant