docs(core): update wording in ComponentDecorator#57878
Closed
ChinoUkaegbu wants to merge 1 commit intoangular:mainfrom
Closed
docs(core): update wording in ComponentDecorator#57878ChinoUkaegbu wants to merge 1 commit intoangular:mainfrom
ChinoUkaegbu wants to merge 1 commit intoangular:mainfrom
Conversation
14 tasks
JeanMeche
approved these changes
Sep 19, 2024
JeanMeche
approved these changes
Sep 19, 2024
Member
|
caretaker note: docs-only change, no presubmit required |
pkozlowski-opensource
approved these changes
Sep 23, 2024
Member
|
This PR was merged into the repository by commit d30cef2. The changes were merged into the following branches: main, 18.2.x |
|
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. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
The documentation insists that a component must belong to an NgModule in order for it to be available to another component or application.
Issue Number: #57689
What is the new behavior?
The documentation still provides instructions to make a component a member of an NgModule, but only when running Angular with NgModule
Does this PR introduce a breaking change?
Other information
Replacement for #57709