Skip to content

Conversation

@ChadKillingsworth
Copy link
Collaborator

Goes along (but does not require) #2094 and #2130.

When updating type node annotations during module rewriting, treat any type name with a / as a module identifier. Needed for named modules loaded from a registry.

Example /** @type {!page/index.Context} */

@brad4d brad4d self-assigned this Nov 14, 2016
@brad4d
Copy link
Contributor

brad4d commented Nov 14, 2016

I'm importing & testing this PR now.

@brad4d
Copy link
Contributor

brad4d commented Nov 15, 2016

@ChadKillingsworth
All tests passed and LGTM, but why no test cases? Are they included in your related PRs?

@ChadKillingsworth
Copy link
Collaborator Author

@brad4d Tests would be dependent on the other PRs. We can sit on this until then if you wish. Or I can add tests as a separate pr after everything lands.

Mainly I needed this functionality on my code base.

@brad4d
Copy link
Contributor

brad4d commented Nov 15, 2016

@ChadKillingsworth
I'm fine with submitting it now.
I'm just waiting for an LGTM from @MatrixFrog

@brad4d
Copy link
Contributor

brad4d commented Nov 15, 2016

This has been submitted internally.

@blickly blickly closed this in 3cd1d3d Nov 15, 2016
@ChadKillingsworth ChadKillingsworth deleted the module-type-annotations branch November 30, 2016 02:32
alexeykomov pushed a commit to alexeykomov/closure-compiler that referenced this pull request Feb 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants