From 8f6560857cc9dfd38daa878f4683d58970d1feeb Mon Sep 17 00:00:00 2001 From: Andrew Seguin Date: Tue, 3 Sep 2024 14:28:04 -0600 Subject: [PATCH] docs: reword when to use model inputs (#57648) PR Close #57648 --- adev/src/content/guide/signals/model.md | 10 ++++------ 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/adev/src/content/guide/signals/model.md b/adev/src/content/guide/signals/model.md index 10a8558e343..142d53b08e3 100644 --- a/adev/src/content/guide/signals/model.md +++ b/adev/src/content/guide/signals/model.md @@ -130,9 +130,7 @@ through the template. ## When to use model inputs -Use model inputs in components that exist to modify a value based on user interaction. -Custom form controls, such as a date picker or combobox, should use model inputs for their -primary value. - -Avoid using model inputs as a convenience to avoid introducing an additional class property for -containing local state. +Use model inputs when you want a component to support two-way binding. This is typically +appropriate when a component exists to modify a value based on user interaction. Most commonly, +custom form controls such as a date picker or combobox should use model inputs for their primary +value.