JNetReflector check the beginning of TypeName#923
Merged
masesdevelopers merged 7 commits intomasterfrom Apr 8, 2026
Merged
Conversation
Instead to check the full equivalence of type name, the new check verify if type name starts with one of the excluded class: if the containing class is in the list of avoided classes, the nested classes, which starts with the same type name of its containing class, shall be avoided too otherwise there isn't a container in C# to allocated nested classes. Within the check a class load error was discovered since the class received from the function JVMClass can receive a type containing the definition of a generic type: to avoid load problem if the type contains a possible generic definition the type name is updated and the class is loaded using the raw type name.
masesdevelopers
added
bug
masesdevelopers
deleted the
897-nested-classes-are-not-removed-from-reflection-setting-its-container-class
branch
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Instead to check the full equivalence of type name, the new check verify if type name starts with one of the excluded class: if the containing class is in the list of avoided classes, the nested classes, which starts with the same type name of its containing class, shall be avoided too otherwise there isn't a container in C# to allocated nested classes.
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: