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

fix: allow records as configuration holder #1119

Merged
merged 1 commit into from
Aug 23, 2023

Conversation

fbricon
Copy link
Contributor

@fbricon fbricon commented Aug 22, 2023

Fixes #1118

@angelozerr what should happen if neither sourceField nor sourceMethod can be found? Should we stop processing for that javaElement?

Signed-off-by: Fred Bricon [email protected]

@sonarcloud
Copy link

sonarcloud bot commented Aug 22, 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

@angelozerr
Copy link
Contributor

LGTM

@angelozerr what should happen if neither sourceField nor sourceMethod can be found? Should we stop processing for that javaElement?

If I remember in JDT, my idea was to provide the jump to definition to the java type even if the field or the record cannot be found.

@fbricon fbricon marked this pull request as ready for review August 23, 2023 07:19
@fbricon fbricon merged commit 5a3bcbd into redhat-developer:main Aug 23, 2023
11 checks passed
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.

NPE when using records as configuration holder
2 participants