Skip to content
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.

Sign up for GitHub

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

Jump to bottom

In the Closure dictionary, make the 'private' tag more flexible #730

Closed
hegemonic opened this issue Aug 13, 2014 · 0 comments
Closed

In the Closure dictionary, make the 'private' tag more flexible #730

hegemonic opened this issue Aug 13, 2014 · 0 comments
Labels
bugfix
Milestone
3.3.0

Comments

@hegemonic
Copy link
Contributor

Closure Compiler seems to treat @private {string} as equivalent to @private @type {string}. Need to update the Closure Compiler tag dictionary accordingly.
@hegemonic hegemonic changed the title In the Closure dictionary, make the In the Closure dictionary, make the 'private' tag more flexible Aug 13, 2014
@hegemonic hegemonic added this to the 3.3.0 milestone Aug 13, 2014
This was referenced Aug 13, 2014
Closed
Closed
hegemonic added a commit that referenced this issue Aug 13, 2014
@hegemonic
allow the Closure version of the private tag to specify a type (#730)
21e0dba
@hegemonic hegemonic mentioned this issue Aug 13, 2014
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bugfix
Projects
None yet
Milestone
3.3.0
Development

No branches or pull requests
1 participant
@hegemonic