You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am having issues understanding the parsing of annotations when using nested modules, namespaces, etc. The usage of memberof .. etc. renders the content properly using jsdoc but not in docma which uses jsdoc-x.
I will be pasting screenshots from docma as it easily shows the intended behaviour and will paste the output from running jsdoc-x as well in the end.
in the jsdoc-x output, the memberof field decides where the symbol will go as a child. You might also have to use memberof! (with exclamation) to force hierarchy on object properties. Do you have a bmrExtension.module:stores symbol in the output?
Hello,
I am having issues understanding the parsing of annotations when using nested modules, namespaces, etc. The usage of
memberof
.. etc. renders the content properly usingjsdoc
but not in docma which uses jsdoc-x.I will be pasting screenshots from docma as it easily shows the intended behaviour and will paste the output from running
jsdoc-x
as well in the end.I have a main namespace defined as:
And then two namespaces
bmrExtension.uikit
andbmrExtension.profile
and modulesacl
andloggers
defined as:The module loggers itself has members and so far everything renders nicely.
Now, I want to add a new module that is a
memberof
the main namespacebmrExtension
and has a bunch of members.and then I have:
and this is where it becomes interesting:
only two are nested properly, one is completely missing and two are nested wrongly.
When I try and render using
jsdoc
I get the correct member hierarchy:Running the parser directly
Would love to hear your thoughts on this.
The text was updated successfully, but these errors were encountered: