Skip to content

Typo in 2.0.0-beta.3 release notes #3963

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

Closed
xuanshenbo opened this issue Apr 8, 2017 · 1 comment · Fixed by #3966
Closed

Typo in 2.0.0-beta.3 release notes #3963

xuanshenbo opened this issue Apr 8, 2017 · 1 comment · Fixed by #3966

Comments

@xuanshenbo
Copy link

xuanshenbo commented Apr 8, 2017

Bug, feature request, or proposal:

Two typos found in the release notes

What is the expected behavior?

Under the Angular 4 section, the second bullet point.
users of @angular/material
need to explicitly import BrowserAnimationsModule (or NoopAnimationsModule) from
@angular/package-browser/animations as well as installing @angular/animations.

Should be:
users of @angular/material
need to explicitly import BrowserAnimationsModule (or NoopAnimationsModule) from
@angular/platform-browser/animations as well as installing @angular/animations.

i.e. @angular/package-browser/animations should be @angular/platform-browser/animations

@import '~@angular/material/prebuilt-themes/deeppurple-amber.css';
should be
@import '~@angular/material/prebuilt-themes/deeppurple-amber';

What is the current behavior?

See above

What are the steps to reproduce?

What is the use-case or motivation for changing an existing behavior?

Which versions of Angular, Material, OS, browsers are affected?

Is there anything else we should know?

@angular-automatic-lock-bot
Copy link

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 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant