diff --git a/examples/Demo/Shared/Pages/FormsOverviewPage.razor b/examples/Demo/Shared/Pages/FormsOverviewPage.razor index b96d1ef3a3..1708230407 100644 --- a/examples/Demo/Shared/Pages/FormsOverviewPage.razor +++ b/examples/Demo/Shared/Pages/FormsOverviewPage.razor @@ -12,7 +12,7 @@
@@ -96,7 +96,7 @@ For a checkbox it is displayed after the input field, for a switch it is displayed in front of it.Note: When using the input components in SSR mode, be sure to assing a value to the
Nameproperty otherwise the - enhanced form functionalty will not work. In contrast to the standard Blazor input components a name is not automatically being + enhanced form functionalty will not work. In contrast to the standard Blazor input components a name is not automatically being generated. Also, theNameneeds to be prefixed with the model name (i.e. `Model.Username`).
- If you would like to apply more complex markup for the label, you can use the LabelTemplate parameter. As this has a type of
+ If you would like to apply more complex markup for the label, you can use the LabelTemplate parameter. As this has a type of
RenderFragment?, it can contain virtuall anything.
@@ -137,12 +137,17 @@
+ The FluentEditForm inherits from the standard EditForm. The only thing it does is that it add a cascading parameter that contains a FluentWizardStep we use to register a form inside a FluentWizard.
+
If you are not using a FluentWizard in your form, there is no need/use to use the FluentEditForm
FluentValidationSummary and FluentValidationMessage to give feedback on the state of the form. It
+ components. It uses the FluentValidationSummary and FluentValidationMessage to give feedback on the state of the form. It
uses the same Starship model as the standard docs and a DataAnnotationsValidator to use the data annotations set in the model.
Not all of the library's input components are used in this form. No data is actually being stored or saved.