Replies: 2 comments 3 replies
-
It did seem that nested namespaces got a few bugs in certain edge cases. @NanoBob, are you still willing to contributing fixes? Learn comes with a dedicated API browser page that lists all the namespaces, is this something folks generally wants? |
Beta Was this translation helpful? Give feedback.
2 replies
-
I am definitely willing to contribute fixes @yufeih. @paytools-master, could you confirm if my understanding of your issue is correct: Let's say you have the following:
Would this be the situation where it goes wrong? And the following would work correctly:
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi - I am very keen to use a nested layout for API documentation and have tried setting the "namespaceLayout" value in the "metadata" config section to "nested". This has the desired effect but true to the warning "Nested namespace is experimental and may produce undesired result.", if there are no types in the root of a given namespace, then the nesting fails to operate and the traditional individual namespace layout is shown.
Can I ask what the status of this feature is please? Should I raise the above as an issue?
Whilst considering API TOC, I note that Microsoft Learn operates a flat TOC for .NET types (i.e., omitting namespaces). Are there any plans to provide this capability within DocFX?
Beta Was this translation helpful? Give feedback.
All reactions