docs: fix embedded view description issue#46957
docs: fix embedded view description issue#46957AlirezaEbrahimkhani wants to merge 2 commits intoangular:mainfrom
Conversation
There was a problem hiding this comment.
This is a bit of a run on sentence that adds a bit too much. We don't really need to specify in the description here what the arguments are, as that's in the section just below this. I actually think the original text is cleaner here. Can you maybe take a second look here?
There was a problem hiding this comment.
What about:
Instantiates an unattached embedded view based on this template.
or
Instantiates an embedded view based on this template that is unattached from a view container.
There was a problem hiding this comment.
I like the first one better. It's clear and concise.
createEmbeddedView method instantiates an embedded view based on this template and take your templateRef as argument and would render the passed templateRef in your ViewContainerRef. resolves angular#46955
5fd6b0a to
6fc1475
Compare
I've pushed a fixup making my review invalid.
|
@AndrewKushnir @jessicajaniuk |
|
@Achilles1515 thanks for the comment. You are right, I misread the sentence, the "and attaches it to the view container" should be removed, so the description should say |
|
We were also going to add "unattached" to the description for increased clarification.
|
6fc1475 to
8dc2498
Compare
|
@Achilles1515 Thanks for catching this before we merged it. I've replaced the fixup commit and updated with exactly that language. |
|
This PR was merged into the repository by commit 5509e35. |
|
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. |
createEmbeddedView method instantiates an embedded view based on this template and take your templateRef as argument and would render the passed templateRef in your ViewContainerRef.
resolves #46955
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?
Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
Other information