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
Is there a YUIDoc technique that would allow me to document a "foo.Object" class, while using the "foo" module namespace, and get links to that class page, rather than YUIDoc thinking I mean the JavaScript Object?
In other words, if I document a class like this:
/**
@class Object
@module foo
@constructor
*/
Then reference it like this (while implying on the namespace):
{{#crossLink "Object"}}{{/crossLink}}
then, understandably, YUIDoc thinks I'm referencing the JavaScript native "Object".
Is there a way to force YUIDoc to infer my foo.Object object from this crosslink?
The text was updated successfully, but these errors were encountered:
xeolabs
changed the title
How to document "foo.Object", with crosslinks, without specifying "foo"?
How to document and crosslink my "foo.Object" class?
Nov 13, 2016
Is there a YUIDoc technique that would allow me to document a "foo.Object" class, while using the "foo" module namespace, and get links to that class page, rather than YUIDoc thinking I mean the JavaScript Object?
In other words, if I document a class like this:
Then reference it like this (while implying on the namespace):
then, understandably, YUIDoc thinks I'm referencing the JavaScript native "Object".
Is there a way to force YUIDoc to infer my
foo.Object
object from this crosslink?The text was updated successfully, but these errors were encountered: