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

Lower severity for missing framework parameter logging to DEBUG #1506

Merged
merged 1 commit into from
Jul 3, 2023

Conversation

MikeEdgar
Copy link
Member

Closes #1264

Log a slightly modified message at DEBUG when a @Parameter is found without an equivalent framework parameter, e.g. @PathParam. Using @Parameter as a standalone annotation has valid use cases (see #1264) and should not be logged as a warning.

@MikeEdgar MikeEdgar added this to the 3.4.1 milestone Jun 30, 2023
Signed-off-by: Michael Edgar <michael@xlate.io>
@sonarcloud
Copy link

sonarcloud bot commented Jun 30, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 0 Code Smells

No Coverage information No Coverage information
0.0% 0.0% Duplication

Copy link
Member

@phillip-kruger phillip-kruger left a comment

Choose a reason for hiding this comment

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

LGTM

@phillip-kruger phillip-kruger merged commit 4d818b1 into smallrye:main Jul 3, 2023
8 checks passed
@MikeEdgar MikeEdgar deleted the issue-1264 branch July 3, 2023 10:56
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.

Standalone @Parameter annotation and warning logs
2 participants