Repository navigation
Create a linter for correct g-c-j usage #2018
Copy link
Copy link
Closed
Labels
priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.
Description
Activity
- addedtype: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.
on May 1, 2017 - addedpriority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.
on May 8, 2017 garrettjonesgoogle commented
on Aug 11, 2017 ContributorAuthorMore actionsThis has been added to our feature backlog: https://github.com/GoogleCloudPlatform/google-cloud-java/wiki/Feature-backlog . This issue will be closed but is linked in the backlog and can continue to be used for comment and discussion.
- added 2 commits that reference this issue
on Feb 20, 2026 - added a commit that references this issue
on Mar 23, 2026 - added 2 commits that reference this issue
on Mar 24, 2026
Metadata
Metadata
Assignees
Labels
priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.‘Nice-to-have’ improvement, new feature or different behavior or design.
We should create a linter that can detect usage of google-cloud-java that is problematic. Specifically, some users will want to make sure they don't use any
@BetaApifeatures, so the linter should support detection of that in user code.