Reflection.properties returns different results on first and following calls #6
Conversation
This file contains 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
ubald
changed the title
|
I fixed it by moving some code around in order to first get all the properties and then store that result. Instead of having a mix of fetching+caching only the top level and fetching the rest without caching it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Sorry for doing it like this, issues are disabled.
So using
Reflection.propertiesorReflection.getcaches the results, but only the result of the top class are cached. So the first call returns all properties in the class hierarchy, but the second call only return properties of the top class. It should always return the same thing, my preference being all the properties.