Skip to content

fix(compiler): support referencing enums in namespaces - #20947

Closed
chuckjaz wants to merge 1 commit into
angular:masterfrom
chuckjaz:i18170
Closed

chuckjaz wants to merge 1 commit into
angular:masterfrom
chuckjaz:i18170

Conversation

@chuckjaz

@chuckjaz chuckjaz commented Dec 11, 2017 •

Copy link
Copy Markdown
Contributor

Due to an overly agressive assert the compiler would generate
an internal error when referencing an enum declared in
namspace.

Fixes #18170

PR Type

What kind of change does this PR introduce?

[x] Bugfix

What is the current behavior?

Issue Number: #18170

What is the new behavior?

The assert is removed and change to remove the members before loading the summary for a enum reference.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

@chuckjaz chuckjaz added the target: patch This PR is targeted for the next patch release label Dec 11, 2017
@mary-poppins

Copy link
Copy Markdown

You can preview 278fe57 at https://pr20947-278fe57.ngbuilds.io/.

@jasonaden jasonaden added the area: core Issues related to the framework runtime label Dec 11, 2017
@vicb

vicb commented Dec 12, 2017

Copy link
Copy Markdown
Contributor

from @chuckjaz: travis failing is not related to the PR

Due to an overly agressive assert the compiler would generate
an internal error when referencing an enum declared in
namspace.

Fixes angular#18170
@chuckjaz chuckjaz added the action: merge The PR is ready for merge by the caretaker label Dec 12, 2017
@mary-poppins

Copy link
Copy Markdown

You can preview a90a343 at https://pr20947-a90a343.ngbuilds.io/.

jasonaden pushed a commit that referenced this pull request Dec 13, 2017
Due to an overly agressive assert the compiler would generate
an internal error when referencing an enum declared in
namspace.

Fixes #18170

PR Close #20947
@jasonaden jasonaden closed this in 634d33f Dec 13, 2017
@imcotton

Copy link
Copy Markdown
Contributor

Any chance to get it back port to v4?

@angular-automatic-lock-bot

Copy link
Copy Markdown

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot Bot locked and limited conversation to collaborators Sep 13, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: core Issues related to the framework runtime cla: yes target: patch This PR is targeted for the next patch release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

ERROR in Illegal state: symbol without members expected when using AOT in 4.3.0

6 participants