Skip to content
This repository has been archived by the owner on Aug 9, 2022. It is now read-only.

Implement support for generic inheritance #8

Open
steffen-wilke opened this issue Apr 5, 2019 · 4 comments
Open

Implement support for generic inheritance #8

steffen-wilke opened this issue Apr 5, 2019 · 4 comments

Comments

@steffen-wilke
Copy link

steffen-wilke commented Apr 5, 2019

Currently, a generic inheritance isn't properly resolved to a link.

Example:
image

Expected for the Example:

Inheritance
-----------------------------------------------
ClientMessageHandler<PingResponseMessage>
↳ PingLoop

with a link to de.gurkenlabs.litiengine.net.messages.handlers.ClientMessageHandler.html and de.gurkenlabs.litiengine.net.messages.PingResponseMessage.html

@andrei-punko
Copy link
Contributor

I generated DocFx yml files for litiengine source repo; yml file for PingLoop class contains all required items in references section with next uids:

  • de.gurkenlabs.litiengine.net.messages.handlers.ClientMessageHandler<de.gurkenlabs.litiengine.net.messages.PingResponseMessage>
  • de.gurkenlabs.litiengine.net.messages.handlers.ClientMessageHandler
  • de.gurkenlabs.litiengine.net.messages.PingResponseMessage

In addition yml files for both ClientMessageHandler and PingResponseMessage classes generated too.

So from doclet perspective it's clear, We need to confirm does DocFx supports of clickable items in inheritance hierarchy as did in interfaces section, @dendeli-msft and @superyyrrzz

@superyyrrzz
Copy link
Collaborator

I think it can work if there is a specName illustrating each part in reference section.

@andrei-punko
Copy link
Contributor

@superyyrrzz , could you clarify this specName approach on example please

@superyyrrzz
Copy link
Collaborator

# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants