allow serialization config to contain java source style syntax classnames #3048
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
kkriske
force-pushed
the
serialization-config-friendly-syntax
branch
from
61d72c6 to
638f44e
Compare
olpaw
approved these changes
Dec 11, 2020
|
Your commit made it on master: 9e00386 |
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.
Similar to how jni and reflection config files allow references like
org.example.ClassName[]instead of[org.example.ClassName;, this should also be allowed for the serialization config.The added code is copied from
com.oracle.svm.hosted.config.ReflectionRegistryAdapter#resolveTypeResultwhich is where these cases for reflection/jni are handled.