Add setting to make new classes package-private instead of public - #4484
Merged
datho7561 merged 2 commits intoAug 13, 2026
Conversation
…e-private visibility
MeherSru
marked this pull request as ready for review
August 13, 2026 16:10
Contributor
|
|
Contributor
|
Fixes #3870 |
datho7561
approved these changes
Aug 13, 2026
datho7561
left a comment
datho7561
left a comment
Contributor
There was a problem hiding this comment.
Looks good and works well. Thanks, Meher!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds a new setting: java.templates.preferPackagePrivateVisibility
When turned on, new Java files (class/interface/enum/record) won't
be created with "public" anymore. They'll be package-private instead.