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

Disable non-public properties, rather than private #829

Merged
merged 2 commits into from
Jun 22, 2021

Conversation

Azquelt
Copy link
Contributor

@Azquelt Azquelt commented Jun 21, 2021

Update the private-properties.enable config property to enable or
disable non-public properties, rather than just private ones.

Fixes #825

There wasn't much feedback on the issue so I've gone ahead and created this PR which changes the meaning of private-properties.enable to affect all non-public properties. Let me know if you'd prefer this was fixed in a different way, e.g. by introducing separate properties to configure protected or package scoped properties.

Update the private-properties.enable config property to enable or
disable non-public properties, rather than just private ones.
@Azquelt Azquelt force-pushed the ignore-non-public-properties branch from 5da34fd to 48a00da Compare June 21, 2021 17:06
@Azquelt
Copy link
Contributor Author

Azquelt commented Jun 21, 2021

The build check failed to download an artifact from maven central, repushed to prompt it to have another go...

Copy link
Member

@MikeEdgar MikeEdgar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, thanks @Azquelt

@phillip-kruger phillip-kruger added this to the 2.1.7 milestone Jun 22, 2021
@phillip-kruger phillip-kruger merged commit 284fbb2 into smallrye:main Jun 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Non-public properties are included the generated OpenAPI document
3 participants