[resolvers] Add avoidCheckingAbstractTypesRecursively
option to support nested defaultMappers
#10141
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.
Description
Related #10084
In #10014, we fixed an issue where nested abstract types were not getting the correct types. This, however, caused existing usage of nested
defaultMapper
to be in an infinite loop.This PR adds
avoidCheckingAbstractTypesRecursively
option to preserve the existingdefaultMapper
behaviours by setting totrue
Type of change
How Has This Been Tested?