| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
| Error handling isn't limited to template syntax. If you are creating components or embedded views dynamically using `ViewContainerRef` or the standalone `createComponent` function, you can provide an `onError` callback in the options object. This callback functions identically to an `@error` block but for imperatively created views. | ||
|
|
||
| ```ts | ||
| viewContainerRef.createComponent(DynamicComponent, { |
There was a problem hiding this comment.
I think we can also avoid the "Component" suffix here
| viewContainerRef.createComponent(DynamicComponent, { | |
| viewContainerRef.createComponent(Dynamic, { |
Sorry, something went wrong.
There was a problem hiding this comment.
AGENT: Thank you for putting together the documentation for @boundary!
Overall, the content is well-structured and provides a clear overview of error boundaries in Angular templates. I have left inline suggestions focused on alignment with the Angular Documentation Style Guide and Google Technical Writing guidelines (sentence case in headings, present tense instead of future "will", active voice, avoiding Latin abbreviations and casual idioms).
Key highlights:
Sorry, something went wrong.
|
This PR was merged into the repository. The changes were merged into the following branches:
|
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
No description provided.