-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Closure Compiler punch list #605
Comments
It would be nice to have these, but some are obviously very non-trivial to implement. Is there a way we can suppress |
hegemonic
pushed a commit
that referenced
this issue
Aug 25, 2016
This commit adds support for specifying an Array of tags which are unknown to JSDoc, but allowed without error. It provides a more granular way to disable such errors while retaining the benefits of catching errant tags (e.g. typos). The intended use case is catching errant tags when using additional tools which support tags not recognized by JSDoc (e.g. Closure Compiler and the tags discussed in #605). Signed-off-by: Kevin Locke <kevin@kevinlocke.name>
hegemonic
added a commit
that referenced
this issue
Jul 16, 2017
hegemonic
added a commit
that referenced
this issue
Jul 16, 2017
hegemonic
added a commit
that referenced
this issue
Jul 16, 2017
hegemonic
added a commit
that referenced
this issue
Jul 16, 2017
hegemonic
added a commit
that referenced
this issue
Jul 17, 2017
hegemonic
added a commit
that referenced
this issue
Jul 17, 2017
hegemonic
added a commit
that referenced
this issue
Jul 17, 2017
hegemonic
added a commit
that referenced
this issue
Jul 17, 2017
hegemonic
added a commit
that referenced
this issue
Jul 17, 2017
hegemonic
added a commit
that referenced
this issue
Jul 17, 2017
hegemonic
added a commit
that referenced
this issue
Jul 17, 2017
hegemonic
added a commit
that referenced
this issue
Jul 17, 2017
hegemonic
added a commit
that referenced
this issue
Jul 17, 2017
hegemonic
added a commit
that referenced
this issue
Jul 17, 2017
hegemonic
added a commit
that referenced
this issue
Jul 17, 2017
hegemonic
added a commit
that referenced
this issue
Jul 17, 2017
hegemonic
added a commit
that referenced
this issue
Jul 17, 2017
hegemonic
added a commit
that referenced
this issue
Jul 17, 2017
hegemonic
added a commit
that referenced
this issue
Jul 21, 2017
hegemonic
added a commit
that referenced
this issue
Jul 21, 2017
hegemonic
added a commit
that referenced
this issue
Jul 22, 2017
hegemonic
added a commit
that referenced
this issue
Jul 22, 2017
Fixed on master. JSDoc 3.6.0 will include support for the new tags. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue tracks adding support for all of the documented Google Closure Compiler annotations.
Tags
@const
@constructor
@define
@deprecated
@dict
@enum
@export
@extends
@externs
@fileoverview
@final
@implements
(@implements (Interfaces) #375)@implicitCast
@inheritDoc
(@inheritDoc and @override tags support. #53)@interface
(@implements (Interfaces) #375)@lends
@license
@modifies
@noalias
@nocollapse
@nocompile
@nosideeffects
@override
(@inheritDoc and @override tags support. #53)@package
(add support for @package access #962)@param
@polymer
@polymerBehavior
@preserve
(synonym for@license
)@private
(needs to accept a type) (In the Closure dictionary, make the 'private' tag more flexible #730)@protected
(needs to accept a type) (For Closure, the 'protected' tag should accept a type #731)@public
@record
(partial synonym for@interface
; see Structural Interfaces in Closure Compiler for details)@return
@struct
@suppress
@template
(Support Closure Compiler generic types #567)@this
(implemented, but with different semantics)@throws
@type
(needs to accept a description) (For Closure, allow the 'type' tag to have a description #732)@typedef
(implemented, but with different semantics)@unrestricted
Other annotation
Miscellaneous
Run JSDoc on Closure Library with 0 warningsGenerate useful documentation by running JSDoc on Closure LibraryThe text was updated successfully, but these errors were encountered: