Fix code analysis not correctly detecting base types when inline constructors are used #279
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.
At present, when a class uses an inline constructor (see examples below), the base class or interface would not be detected correctly, and incorrectly return
object
. This is due to an out of date library. This PR updates the library, and fixes a resultant error (there are now two overloads ofGetAccessibleMembersInThisAndBaseTypes()
)In the above, the CustomPipeline should only document classes the extend the
OtherClass
base type. At present,MyClass
is not documented despite extending the correct base type. This PR fixes this issue.