docs: add warning when using Unpatch on elements that refer a FormControl (#1665)

Laurens-makel · hoebbelsB · LaurensMakel · web-flow · commit 30b486e3e671 · 2024-02-27T12:42:25.000+01:00
* docs: add warning when using Unpatch on elements that refer a FormControl

* prettier

---------

Co-authored-by: Julian Jandl &lt;julian@jandl.wien&gt;
Co-authored-by: Laurens &lt;hflaurens@hotmail.com&gt;
diff --git a/apps/docs/docs/template/api/unpatch-directive.md b/apps/docs/docs/template/api/unpatch-directive.md
@@ -36,7 +36,10 @@ The `unpatch` directive solves this problem in a convenient way:
 </button>
 ```
 
-> **Warning**: Do not use `[unpatch]` on elements that should trigger navigation (with `routerLink` directly or with method bound to `(click)` or other events). Otherwise you will end up having a 'Navigation triggered outside Angular zone, did you forget to call "ngZone.run()"?' warning.
+> **Warning**: Do not use `[unpatch]` on the following elements:
+>
+> 1. Elements that should trigger navigation (with `routerLink` directly or with method bound to `(click)` or other events). Otherwise you will end up having a 'Navigation triggered outside Angular zone, did you forget to call "ngZone.run()"?' warning.
+> 2. Elements that reference a `FormControl`. Specify all events except the `blur` and `change` events. Otherwise user input is ignored, the `FormControl.valueChanges` observable will not emit and attached validations to the FormControl will not run until next change detection that affects the component in which the element is rendered.
 
 Included Features:
 
