-
Notifications
You must be signed in to change notification settings - Fork 6.8k
fix(icon): server-side error when registering icons #8492
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
Conversation
jelbourn
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
Any ETA when this will make it into a release? This is blocking our migration to Universal, so it would be good to know if I just wait another day or look for a different solution. |
|
This is a major change due to the constructor being altered, seeing breaking tests internally due to subclasses breaking |
|
Constructor change could be avoided by not using the injected document |
ec0df1a to
ae07b22
Compare
|
Reworked it to avoid the breaking change. Switching back to patch release. |
Fixes an error that is thrown by the `IconRegistry` when registering icons on the server side. Fixes angular#6787.
ae07b22 to
3cac816
Compare
Fixes an error that is thrown by the `IconRegistry` when registering icons on the server side. Fixes angular#6787.
Fixes an error that is thrown by the `IconRegistry` when registering icons on the server side. Fixes angular#6787.
Fixes an error that is thrown by the `IconRegistry` when registering icons on the server side. Fixes #6787.
Fixes an error that is thrown by the `IconRegistry` when registering icons on the server side. Fixes #6787.
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Fixes an error that is thrown by the
IconRegistrywhen registering icons on the server side.Fixes #6787.