Brendan
Brendan
We could do that. I've been think on ways to refactor this ext. My priorities are 1. better parsing mechanism 2. specify an entity via user friendly implementation The database...
> To be clear, by better parsing mechanism, is that in regards to the doxygen syntax Yes. I'm not sure how the C++ parsing would need improvement. I still want...
> currently the symbol tree only gets populated as the c++ domain directives are actually run I noticed that. Is there a reason you don't just save the parsed API...
Well I'm ok with this getting merged but there should be a warning on both config and demo doc pages. Possibly even a warning in the build log like you...
Instead of a task list in the thread OP, you could use a [github project](https://docs.github.com/en/issues/planning-and-tracking-with-projects/learning-about-projects/about-projects) to track the progress of this extension.
Did I mess up the rebase?
I thought it was weird when the rebased push didn't trigger the CI (only RTD's CI ran).
I can try to fix the content tabs so that inline RST roles should work. There may be some roles that you shouldn't need to use in the labels for...
I was able to get the roles parsed properly when treating the raw text as a separate paragraph. This results in a automatic `` element that triggers builtin CSS: ...
That's what it is using now; it doesn't seem to handle parsing roles. unless I appended the children improperly somehow.