chore: Add support for derivedClasses
metadata when implements interfaces
#10632
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.
This PR intended to fix a part of issue that is reported at #2531
Currently docfx generate
derivedClasses
metadata when inherited from class.But
derivedClasses
metadata is not outputted for interface implements.This PR add
derivedClasses
support for interfaces.Additionally, Replace dictionary lookup logics to use
CollectionsMarshal.GetValueRefOrAddDefault
to reduce dictionary double-lookup costs.
Test
I've manually confirmed
derivedClasses
metadata generation with following sample code.And confirmed metadata is generated as expected.
TODO
Currently
derivedClasses
metadata information is not rendered for interface HTML page.It need to modify docfx templates also (by another PR)