Skip to content
This repository has been archived by the owner on Feb 26, 2024. It is now read-only.

Rename goog.provide from 'global' to 'globalNs' #931

Merged
merged 1 commit into from
Oct 8, 2019

Conversation

lauraharker
Copy link
Contributor

A Closure Compiler change will begin special casing 'global' as it is native to Node environments. This causes issues when trying to goog.provide it. See also discussion on Google internal
https://cl/270391864.

A Closure Compiler change will begin special casing 'global' as it is
a built-in in Node environments. See Google internal
https://cl/270391864.
@lauraharker lauraharker marked this pull request as ready for review October 7, 2019 21:23
@mprobst
Copy link
Contributor

mprobst commented Oct 8, 2019

@rkirov sonatype apparently has a hiccup again. Can we maybe disable the snapshot test to unblock changes while we move to internal first?

@rkirov
Copy link
Contributor

rkirov commented Oct 8, 2019

Yes, but note that test_released doesn't really pass (green check-mark is showing because it is optional). Making released always pass is at odds with g3 passing tests after sync which runs at head only. Mostly because of golden tests against externs, we can't make a single golden pass against two versions of the JS compiler.

The only way out I see is to prioritize moving to internal first clutz/gents development.

@rkirov
Copy link
Contributor

rkirov commented Oct 8, 2019

For now, I removed the requirement of "ci/circleci: test_snapshot" passing, so that we can merge trivial changes like this one.

@rkirov rkirov merged commit 2d1c04c into angular:master Oct 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants