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
Upgrade documentation is conflicting as to which framework should be bootstrapped first #23225
Comments
Ooops! Good catch 👍 Would you be up to submitting a PR fixing the docs? |
Sure, I'll put together a PR. |
Clarify that Angular should be bootstrapped before AngularJS. Closes angular#23225
Clarify that Angular should be bootstrapped before AngularJS. Closes angular#23225
Clarify that Angular should be bootstrapped before AngularJS. Closes angular#23225
… (angular#23270) Clarify that Angular should be bootstrapped before AngularJS. Closes angular#23225 PR Close angular#23270
… (angular#23270) Clarify that Angular should be bootstrapped before AngularJS. Closes angular#23225 PR Close angular#23270
… (angular#23270) Clarify that Angular should be bootstrapped before AngularJS. Closes angular#23225 PR Close angular#23270
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. |
I'm submitting a...
Current behavior
In the documentation for the
UpgradeModule
(https://angular.io/api/upgrade/static/UpgradeModule), in the "Mental Model" section, the page states:However, in the "Example" section that follows, the code and comments seem to suggest the opposite:
Note the comment: "Once Angular bootstrap is complete then we bootstrap the AngularJS module".
Further, the general "Upgrading from AngularJS" documentation page (https://angular.io/guide/upgrade) also seems to suggest that Angular should be bootstrapped first, followed by AngularJS:
Expected behavior
The documentation should be consistent on which framework should be bootstrapped first.
Environment
The text was updated successfully, but these errors were encountered: