style: Use the typeAliasRegistry field in BaseBuilder to avoid ambiguity #2670
Conversation
This file contains hidden or 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
harawata
added a commit
to harawata/velocity-scripting
that referenced
this pull request
Jan 27, 2025
Should fix mybatis#14 and mybatis#15
harawata
added a commit
to harawata/velocity-scripting
that referenced
this pull request
Jan 27, 2025
Should fix mybatis#14 and mybatis#15
This was referenced Jan 27, 2025
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.
The field of TypeAliasRegistry has been defined in the BaseBuilder class, so it can be used directly instead of getting it from the Configuration object. This is a bit weird, so adjust to use the TypeAliasRegistry type field in BaseBuilder directly