Skip to content

Java: Tweak Member.getQualifiedName() #10414

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

Merged
merged 5 commits into from
Sep 14, 2022
Merged

Conversation

igfoo
Copy link
Contributor

@igfoo igfoo commented Sep 14, 2022

It now includes the qualified name of the declaring type, rather than just the name.

It also has some qldoc suggesting that hasQualifiedName is used instead, for efficiency (getQualifiedName has to construct new strings).

It's more efficient, as it doesn't require building intermediate
strings.
It now includes the qualified name of the declaring type.
@@ -0,0 +1,4 @@
---
category: minorAnalysis
Copy link
Contributor

Choose a reason for hiding this comment

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

OOI: Isn't this a breaking change?
A lot of queries could stop working, simply because they defined their classes using Member.getQualifiedName() = foo in the char. predicate.
As a user, I would consider this a breaking change.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Fair point, I'll change it. Thanks!

@igfoo igfoo merged commit b3b1efb into github:main Sep 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants