-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow fully qualified enum, class, structs titles #187
Labels
Comments
5p4k
added a commit
to mittelab/exhale
that referenced
this issue
Mar 9, 2023
By default, the behavior is unchanged, however when set to True, all page titles for structures, unions, classes etc include the namespace as a prefix.
5p4k
added a commit
to mittelab/exhale
that referenced
this issue
Mar 30, 2023
By default, the behavior is unchanged, however when set to True, all page titles for structures, unions, classes etc include the namespace as a prefix.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have items with the same name in different namespaces, e.g.
device1::error
anddevice2::error
.When generating the full unabridged API, I get two entries both named "Enum error" (as it should be). However in this specific case, it is confusing. I tracked this down to
exhale/exhale/graph.py
Line 2503 in ebad897
I would like to be able to produce fully qualified titles for this project. This could very well be a project-level option (having only some items fully qualified may be even more confusing).
I think I could also provide a PR implementing this by adding a page-level customization option
fullyQualifiedTitles
, if that's the way to go about this.On a side note, thank you for all the work put in this project. I got back to this after some years and it had matured so much that I'm now switching over from plain Doxygen:)
The text was updated successfully, but these errors were encountered: