NG Dynamic Forms is a rapid form development library based on the official Angular dynamic forms guide.
It fully automates form UI creation by introducing a set of maintainable form control models and dynamic form control components
Out of the box support is provided for all popular UI libraries including Bootstrap, Foundation, Ionic, Kendo, Material, NG Bootstrap and PrimeNG.
See what's possible by exploring the live demo and the API documentation!
- Getting Started
- Running the Example
- Basic Usage
- UI Modules
- Form Groups
- Form Arrays
- Form Layouts
- Form Control Events
- Custom Templates
- Custom Validators
- Validation Messaging
- JSON Export / Import
- Updating Form Models
- Disabling / Enabling Form Controls
- Text Masks
- Related Form Controls
- Autocompletion
- FAQ
- Appendix
1. Install the core package:
npm install @ng-dynamic-forms/core -S
2. Choose your UI library and install the appropriate package:
npm install @ng-dynamic-forms/ui-bootstrap -S
3. When using SystemJS, update your configuration to import the corresponding UMD bundles:
System.config({
paths: {
"npm:": "node_modules/"
},
map: {
// ...all the rest (Angular, RxJS, etc.)
"@ng-dynamic-forms/core": "npm:@ng-dynamic-forms/core/bundles/core.umd.js",
"@ng-dynamic-forms/ui-bootstrap": "npm:@ng-dynamic-forms/ui-bootstrap/bundles/ui-bootstrap.umd.js",
}
});1. Clone the Git repository:
git clone https://github.com/udos86/ng-dynamic-forms.git
2. Install the npm dependencies:
npm install
3. Build the library:
npm run build:packages
4. Transpile the source code:
npm run watch:sample
5. Run the application:
npm start
1. Import DynamicFormsCoreModule via forRoot() and a UI module:
import { DynamicFormsCoreModule } from "@ng-dynamic-forms/core";
import { DynamicFormsBootstrapUIModule } from "@ng-dynamic-forms/ui-bootstrap";
// ...
@NgModule({
imports: [
DynamicFormsCoreModule.forRoot(),
DynamicFormsBootstrapUIModule,
// ...
]
// ...
})
export class AppModule {}2. Define your dynamic form model:
import {
DynamicFormControlModel,
DynamicCheckboxModel,
DynamicInputModel,
DynamicRadioGroupModel
} from "@ng-dynamic-forms/core";
export const MY_FORM_MODEL: DynamicFormControlModel[] = [
new DynamicInputModel({
id: "exampleInput",
label: "Example Input",
maxLength: 42,
placeholder: "example input"
}),
new DynamicRadioGroupModel<string>({
id: "exampleRadioGroup",
label: "Example Radio Group",
options: [
{
label: "Option 1",
value: "option-1",
},
{
label: "Option 2",
value: "option-2"
},
{
label: "Option 3",
value: "option-3"
}
],
value: "option-3"
}),
new DynamicCheckboxModel({
id: "exampleCheckbox",
label: "I do agree"
})
];3. Create a FormGroup via DynamicFormService:
import { MY_FORM_MODEL } from "./my-dynamic-form.model";
import { DynamicFormControlModel, DynamicFormService } from "@ng-dynamic-forms/core";
export class MyDynamicFormComponent implements OnInit {
formModel: DynamicFormControlModel[] = MY_FORM_MODEL;
formGroup: FormGroup;
constructor(private formService: DynamicFormService) {}
ngOnInit() {
this.formGroup = this.formService.createFormGroup(this.formModel);
}
}4. Add a DynamicFormComponent to your template and bind its [group] and [model] property:
<form [formGroup]="formGroup">
<dynamic-bootstrap-form [group]="formGroup"
[model]="formModel"></dynamic-bootstrap-form>
</form>NG Dynamic Forms is built to provide solid yet unobtrusive support for a variety of common UI libraries:
You can instantly plug in your favorite form controls by installing the appropriate package and its peer dependencies:
npm install @ng-dynamic-forms/ui-<library-name> -S
Now just import the UI module:
@NgModule({
imports: [
DynamicFormsCoreModule.forRoot(),
DynamicFormsBootstrapUIModule,
BrowserModule,
ReactiveFormsModule
],
// ...all remaining definitions
})
export class AppModule {}For creating the form markup all UI modules come with a DynamicFormComponent that can easily be added to
your component template:
<form [formGroup]="formGroup">
<dynamic-bootstrap-form [group]="formGroup"
[model]="formModel"></dynamic-bootstrap-form>
</form>Alternatively you can directly make use of a specific DynamicFormControlComponent to gain more control:
<form [formGroup]="formGroup">
<dynamic-bootstrap-form-control *ngFor="let controlModel of formModel"
[group]="formGroup"
[model]="controlModel"></dynamic-bootstrap-form-control>
</form>Due to technical restrictions or external dependencies still being in development the support of major form controls varies among UI packages. See the following compatibility table:
| ui-basic | ui-bootstrap | ui-foundation | ui-ionic | ui-kendo | ui-material | ui-ng-bootstrap | ui-primeng | |
|---|---|---|---|---|---|---|---|---|
| Checkbox | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Checkbox Group | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Datepicker | * | * | * | ✓ | ✓ | * | ✓ | ✓ |
| Editor | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ |
| File Upload | ** | ** | ** | ✗ | ✓ | ** | ** | ** |
| Input | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Radio Group | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Rating | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ | ✓ |
| Select | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Slider | *** | *** | *** | ✓ | ✓ | ✓ | *** | ✓ |
| Switch | ✗ | ✗ | ✓ | ✓ | ✓ | ✓ | ✗ | ✓ |
| Textarea | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| TimePicker | * | * | * | ✓ | ✓ | * | ✓ | ✓ |
*) datetime controls can be achieved using a DynamicInputModel with inputType: "date" or inputType: "time"
**) file upload controls can be achieved using a DynamicInputModel with inputType: "file"
***) slider controls can be achieved using a DynamicInputModel with inputType: "range"
In order to improve clarity it's often considered good practice to group forms into several logical fieldset sections.
Luckily NG Dynamic Forms supports nesting of form groups out of the box!
1. Declare a DynamicFormGroupModel within your Array<DynamicFormControlModel> and add it's models to the group array:
export const MY_FORM_MODEL: DynamicFormControlModel[] = [
new DynamicFormGroupModel({
id: "formGroup1",
legend: "Form Group 1",
group: [
new DynamicInputModel({
id: "input1",
label: "Nested Input 1"
}),
new DynamicInputModel({
id: "input2",
label: "Nested Input 2"
})
]
}),
new DynamicFormGroupModel({
id: "formGroup2",
legend: "Form Group 2",
group: [
new DynamicInputModel({
id: "input3",
label: "Nested Input 3"
}),
new DynamicInputModel({
id: "input4",
label: "Nested Input 4"
})
]
})
]; 2. Create a FormGroup and add a DynamicFormComponent:
ngOnInit() {
this.formGroup = this.formService.createFormGroup(this.formModel);
}<form [formGroup]="formGroup">
<dynamic-bootstrap-form [group]="formGroup"
[model]="formModel"></dynamic-bootstrap-form>
</form>3. To manipulate an existing DynamicFormGroupModel you can simply use DynamicFormService:
addFormGroupControl(...)insertFormGroupControl(...)moveFormGroupControl(...)removeFormGroupControl(...)
Sometimes forms need to allow the user to dynamically add multiple items of the same kind to it, e.g. addresses, products and so on.
Particularly for this reason Angular provides so called Form Arrays.
Fortunately, NG Dynamic Forms is capable of managing such nested form structures!
1. Add a DynamicFormArrayModel to your form model:
export const MY_FORM_MODEL: DynamicFormControlModel[] = [
new DynamicFormArrayModel({
id: "myFormArray"
})
];2. Add the groupFactory property to the DynamicFormArrayModel and assign a function to it which returns
the structure of a single form array item:
new DynamicFormArrayModel({
id: "myFormArray",
initialCount: 5,
groupFactory: () => {
return [
new DynamicInputModel({
id: "formArrayInput",
label: "Form Array Input"
})
];
}
})3. Create a FormGroup via DynamicFormService and bind it to your component template:
this.formGroup = this.formService.createFormGroup(this.formModel);<form [formGroup]="formGroup">
<dynamic-bootstrap-form [group]="formGroup"
[model]="formModel"></dynamic-bootstrap-form>
<button type="button" (click)="addItem()">Add item</button>
<button type="button" (click)="clear()">Remove all items</button>
</form>4. You can now easily modify your form array with DynamicFormService:
ngOnInit() {
this.arrayControl = this.formGroup.get("myFormArray") as FormArray;
this.arrayModel = this.formService.findById("myFormArray", this.formModel) as DynamicFormArrayModel;
}
addItem() {
this.formService.addFormArrayGroup(this.arrayControl, this.arrayModel);
}
clear() {
this.formService.clearFormArray(this.arrayControl, this.arrayModel);
}Alright, works like a charm!
But what if we want to append an additional remove <button> for each array group?
Particularly for this case you can add a <ng-template> and declare some custom content that is rendered equally for all form array groups:
<form [formGroup]="formGroup">
<dynamic-bootstrap-form [group]="formGroup"
[model]="formModel">
<ng-template modelId="myFormArray">
<button type="button" (click)="onClick()">Label</button>
</ng-template>
</dynamic-bootstrap-form>
</form> Whenever a <ng-template> is applied to a DynamicFormArrayModel, NgTemplateOutletContext is internally bound to
the associated DynamicFormArrayGroupModel.
That means you can access the group object and it's properties by either declaring a local default template variable or individual local template variables.
see chapter on Custom Templates
<form [formGroup]="formGroup">
<dynamic-bootstrap-form [group]="formGroup"
[model]="formModel">
<ng-template modelId="myFormArray" let-group let-index="index" let-context="context">
<button type="button" (click)="removeItem(context, index)">Remove Item</button>
<button type="button" (click)="insertItem(group.context, group.index + 1)">Add Item</button>
</ng-template>
</dynamic-bootstrap-form>
</form> This is extremely useful when you'd like to implement a remove or insert function:
removeItem(context: DynamicFormArrayModel, index: number) {
this.formService.removeFormArrayGroup(index, this.arrayControl, context);
}
insertItem(context: DynamicFormArrayModel, index: number) {
this.formService.insertFormArrayGroup(index, this.arrayControl, context);
}Using DynamicFormService again, you can even change the order of the groups in a form array dynamically:
this.formService.moveFormArrayGroup(index, -1, this.arrayControl, context);When using a NG Dynamic Forms UI package, e.g. ui-bootstrap, all essential form classes of the underlying CSS library
(like form-group or form-control) are automatically put in place for you in the template of the corresponding DynamicFormControlComponent.
Apart from that, NG Dynamic Forms does not make any further presumptions about optional CSS classes and leaves advanced layouting all up to you. That's solid yet unobtrusive.
So let's say we want to implement a beautifully aligned Bootstrap horizonal form...
At first we have to append the mandatory Bootstrap CSS class form-horizontal to the <form> element in our template:
<form class="form-horizontal" [formGroup]="formGroup">
<dynamic-bootstrap-form [group]="formGroup"
[model]="formModel"></dynamic-bootstrap-form>
</form>Now we need to position the <label> and the form-control using the Bootstrap grid system.
But since all the template logic for the form controls is capsuled in the scope of the DynamicFormBootstrapComponent we cannot directly attach those necessary CSS classes to markup.
Don't worry!
By providing the cls and it's nested grid and element configuration objects, NG Dynamic Forms allows us to optionally define additional CSS classes for every DynamicFormControlModel, which are then intelligently appended within the DynamicFormControlComponent template.
We can just pass it as a second constructor parameter of every DynamicFormControlModel, i.e. separation of model and style information remains intact:
new DynamicInputModel(
{
// ... all model configuration properties
},
{
element: {
label: "control-label"
},
grid: {
control: "col-sm-9",
label: "col-sm-3"
}
}
)When developing forms it's often useful to keep track of certain events that occur on a specific form control.
With NG Dynamic Forms you can directly bind the three most common events, blur, change and focus, both on DynamicFormControlComponent and DynamicFormComponent:
<dynamic-material-form [group]="formGroup"
[model]="formModel"
(blur)="onBlur($event)"
(change)="onChange($event)"
(focus)="onFocus($event)"></dynamic-material-form><form [formGroup]="myFormGroup">
<dynamic-material-form-control *ngFor="let controlModel of myFormModel"
[group]="myFormGroup"
[model]="controlModel"
(matEvent)="onMatEvent($event)"></dynamic-material-form-control>
</form>The object passed to your handler function gives you any control and model information needed for further processing.
The $event property even grants access to the original event:
interface DynamicFormControlEvent {
$event: Event | FocusEvent | DynamicFormControlEvent | any;
context: DynamicFormArrayGroupModel | null;
control: FormControl;
group: FormGroup;
model: DynamicFormControlModel;
type: string;
}But when using a UI library usually there are a bunch of additional events provided for certain form control components.
Of course, NG Dynamic Forms won't also let you down here.
All custom UI events are pooled by an individual @Output() utilizing the respective library prefix.
<dynamic-material-form [group]="formGroup"
[model]="formModel"
(matEvent)="onMatEvent($event)"></dynamic-material-form>As already mentioned, NG Dynamic Forms gives you a lot of freedom in adjusting your form layout via CSS classes.
However there are situations where you would like to add custom markup for some of your form controls, as well.
In order to do so, just put a <ng-template> inside your dynamic form control element and set a modelId property to assign it to a certain control.
<form [formGroup]="formGroup">
<dynamic-bootstrap-form [group]="formGroup"
[model]="formModel">
<ng-template modelId="myInput">
<p>Just some custom markup</p>
</ng-template>
</dynamic-bootstrap-form>
</form>Alternatively you can also apply modelType instead of modelId to reuse a template for several form controls of the same type:
<form [formGroup]="formGroup">
<dynamic-bootstrap-form [group]="formGroup"
[model]="formModel">
<ng-template modelType="ARRAY">
<p>Just some custom markup</p>
</ng-template>
</dynamic-bootstrap-form>
</form>And it's getting better!
Since for every template NgTemplateOutletContext is internally bound to the corresponding DynamicFormControlModel you
can use local template variables to reference your models' properties:
<form [formGroup]="formGroup">
<dynamic-bootstrap-form [group]="formGroup"
[model]="formModel">
<ng-template modelId="myInput" let-id="id">
<p>Just some custom markup for {{ id }}</p>
</ng-template>
</dynamic-bootstrap-form>
</form>Still not convinced?
Some UI libraries, e.g. Kendo UI, allow detailed customizing of form controls via template directives.
And you surely don't want to miss out on such a feature, do you?
That's why NG Dynamic Forms can even master this!
All you have to do is to add a as attribute to your template and specifiy the use of it:
<form [formGroup]="formGroup">
<dynamic-kendo-form [group]="formGroup"
[model]="formModel">
<ng-template modelId="myDropDownList" as="kendoDropDownListHeaderTemplate">
<p>My Header Template</p>
</ng-template>
</dynamic-kendo-form>
</form>Finally you can determine whether the template is rendered before or after the actual form control by using the align property:
<form [formGroup]="formGroup">
<dynamic-bootstrap-form [group]="formGroup"
[model]="formModel">
<ng-template modelId="myInput" align="START">
<p>Just some custom markup</p>
</ng-template>
</dynamic-bootstrap-form>
</form>Adding built-in Angular validators to any DynamicFormValueControlModel is plain and simple!
Just reference a function from Validators class by it's name in the validators or asyncValidators configuration object:
new DynamicInputModel({
id: "myInput",
label: "My Input",
validators: {
required: null,
minLength: 3
}
})So far so good!
But what if you'd like to introduce some custom validator as well?
export function customValidator(control: AbstractControl): ValidationErrors | null {
let hasError = control.value ? (control.value as string).startsWith("abc") : false;
return hasError ? {customValidator: true} : null;
}Just use the NG_VALIDATORS or NG_ASYNC_VALIDATORS token to provide your validator function:
@NgModule({
// ...
providers: [
{provide: NG_VALIDATORS, useValue: customValidator, multi: true}
]
})Note: thoughtram.io - Custom Validators in Angular 2
You're now ready to apply your custom validator to your model:
new DynamicInputModel({
id: "myInput",
label: "My Input",
validators: {
customValidator: null
}
})But beware! There's a catch!
Internally NG Dynamic Forms resolves a declared validator by it's function name.
Though when uglifying code for production this information is irretrievably lost.
So to avoid a runtime exception you actually would have to exclude all custom validator function names from mangling:
plugins: [
new webpack.optimize.UglifyJsPlugin({
mangle: {
except: ['customValidator']
}
})
]However when working with Angular CLI currently there's no access to the actual build configuration unless running ng eject.
That's when you should make use of the alternate validator notation:
new DynamicInputModel({
id: "myInput",
label: "My Input",
validators: {
customValidator: {
name: customValidator.name,
args: null
}
}
})Delivering meaningful validation information to the user is an essential part of good form design.
Yet HTML5 already comes up with some native functionality you very likely want to use Angular mechanisms to gain much more control over validation logic and it's corresponding message output.
Avoiding a library too opinionated in the beginning, NG Dynamic Forms has originally been developed without any kind of obtrusive validation message system in mind.
However, due to its very common use case and several developer requests, model-based error messaging has eventually become an optional built-in feature:
Just add an errorMessages object to any DynamicFormValueControlModel and assign error message templates based on Validators names:
new DynamicInputModel({
id: "bootstrapInput",
label: "Example Input",
placeholder: "example input",
validators: {
required: null
},
errorMessages: {
required: "{{label}} is required."
}
})Note: Error message templates allow the following placeholders:
{{ propertyName }}wherepropertyNameis a property of the model, for example{{ label }}.{{ validator.propertyName }}wherepropertyNameis a property of the object returned by validation function, for example{{ validator.requiredPattern }}in case of pattern validator.
Error messaging is automatically enabled whenever errorMessages are declared on a DynamicFormControlModel.
It can also be manually enabled or disabled by binding the hasErrorMessaging property of any DynamicFormControlComponent:
<form [formGroup]="formGroup">
<dynamic-bootstrap-form-control *ngFor="let controlModel of formModel"
[group]="formGroup"
[model]="controlModel"
[hasErrorMessaging]="controlModel.hasErrorMessages"></dynamic-bootstrap-form-control>
</form>Still you are completely free to implement your own validation messaging.
Follow the recommended approach below:
1. Create your own custom validation message component and make it accept a FormControl input:
import { Component, Input } from "@angular/core";
import { FormControl } from "@angular/forms";
@Component({
selector: "validation-message",
templateUrl: "./my-validation-message.html"
})
export class MyValidationMessage {
@Input() control: FormControl;
constructor () {}
}2. Create a template file for your custom validation component and implement it's logic based on the control property:
<span *ngIf="control && control.hasError('required') && control.touched">Field is required</span>3. Define some validators for your DynamicFormControlModel:
new DynamicInputModel({
id: "exampleInput",
label: "Example Input",
placeholder: "example input",
validators: {
required: null
}
})4. Add your validation component aside from the DynamicFormControlComponent in your form component template
and bind the FormControl reference via a local template variable:
<form [formGroup]="formGroup">
<ng-container *ngFor="let controlModel of formModel">
<dynamic-bootstrap-form-control [group]="formGroup"
[model]="controlModel" #componentRef>
<validation-message [control]="componentRef.control"></validation-message>
</dynamic-bootstrap-form-control>
</ng-container>
</form>Sooner or later you likely want to persist your dynamic form model in order to restore it at some point in the future.
That's why all DynamicFormControlModels have been preprared to export properly to JSON:
storeForm() {
let json: string = JSON.stringify(this.formModel);
// ...store JSON in localStorage or transfer to server
}Since a DynamicFormControlModel in NG Dynamic Forms relies on prototypical inheritance and thus is not represented by a simple JavaScript object literal,
recreating a form from JSON unfortunately becomes more complex.
The good news is, that DynamicFormService offers the function fromJSON() to make things short and easy:
restoreForm() {
let json: string;
// ...load JSON from localStorage or server
this.formModel = this.formService.fromJSON(json);
}One of the benefits of using NG Dynamic Forms is that programmatically interacting with your form becomes pretty easy.
Since a DynamicFormControlModel is bound directly to a DOM element via Angular core mechanisms,
changing one of it's properties will immediately trigger an update of the user interface.
But there's one major exception!
NG Dynamic Forms relies on the Angular ReactiveFormsModule. Therefore the value property is not two-way-bound via [(ngModel)] under the hood.
So what if we actually want to update the value of an arbitrary form control at runtime?
At first we need to get a reference to it's DynamicFormControlModel representation.
This can easily be achieved either by
a simple index-based array lookup or through the findById method of DynamicFormService:
this.inputModel = this.formModel[2];this.inputModel = this.formService.findById("myInput", this.formModel) as DynamicInputModel;We now have access to a Rx.Subject named valueUpdates to push new values via next() as well as to listen to new user input via subscribe():
this.inputModel.valueUpdates.next("my new value");
this.inputModel.valueUpdates.subscribe(value => console.log("new value: ", value);At any time we can also safely read the most recent user input from the value property:
let currentValue = this.inputModel.value;Dating back to RC.6, Angular does not allow property bindings of the disabled attribute in reactive forms.
That means changing the corresponding disabled property of a DynamicFormControlModel at runtime won't have any effect.
But similar to updating values NG Dynamic Forms helps you out here
by providing a Rx.Subject named disabledUpdates.
It can be used to programmatically switch the activation state of a form control through a DynamicFormControlModel:
this.inputModel.disabledUpdates.next(true);Whenever an <input> element needs to be filled in a predefined value format, text masks make a nice form enhancement to guide the user.
Since Angular does not deliver an appropriate feature by default, NG Dynamic Forms integrates an external Text Mask directive.
That's why most UI packages demand one additional peer dependency to be installed:
npm install angular2-text-mask --save
You're now capable of adding a mask property to any DynamicInputModel according to Text Mask docs:
new DynamicInputModel({
id: "maskedInput",
label: "Masked Input",
mask: ['(', /[1-9]/, /\d/, /\d/, ')', ' ', /\d/, /\d/, /\d/, '-', /\d/, /\d/, /\d/, /\d/],
}),Please note that some UI libraries like Kendo UI come with their own text mask implementation that may rely on a different text mask string / regex representation.
In many complex forms the activation state of a certain form control depends directly on the value or status of some other form control.
So let's pretend we need to have our textarea myTextArea disabled as soon as the third option of our select menu mySelect is chosen.
Manually implementing such a requirement would be time-consuming and only lead to undesired boilerplate code.
Using NG Dynamic Forms however, you can easily define relations between form controls by declaration:
new DynamicTextAreaModel(
{
id: "myTextArea",
label: "My Textarea",
relation: [
{
action: "DISABLE",
when: [
{
id: "mySelect",
value: "option-3"
}
]
}
]
}The relation property may seem a bit oversized at first sight, but that way it allows the flexible declaration of even multi-related form controls.
So what if the activation state of myTextArea should actually depend on another control myRadioGroup as well?
Just add a second entry to the when array and define how both relations should logically be connected via connective:
new DynamicTextAreaModel(
{
id: "myTextArea",
label: "My Textarea",
relation: [
{
action: "DISABLE",
connective: "AND",
when: [
{
id: "mySelect",
value: "option-3"
},
{
id: "myRadioGroup",
value: "option-4"
}
]
}
]
}
)Adding automatic input completion can be key factor to good user experience (especially on mobile devices) and should always be considered when designing forms.
That's why NG Dynamic Forms keeps you covered here, as well!
Following HTML5 standard behavior, the autocomplete attribute is always bound to on for any DynamicFormTextInputControl form element by default.
Nevertheless you can completely disable this feature by explicitly setting the corresponding model property to off:
import { AUTOCOMPLETE_OFF } from "@ng-dynamic-forms/core";
let model = new DynamicInputModel({
autoComplete: AUTOCOMPLETE_OFF
//...all remaining properties
});Further on NG Dynamic Forms embraces the brand new HTML5
autofill detail tokens by providing
AUTOFILL_<TOKEN_NAME|FIELD_NAME> string constants and AutoFillUtils to help you putting together a valid expression:
Note: Jason Grigsby - Autofill: What web devs should know, but don’t
import {
AutoFillUtils,
AUTOFILL_TOKEN_BILLING,
AUTOFILL_FIELD_NAME,
AUTOCOMPLETE_ON
} from "@ng-dynamic-forms/core";
export class MySample {
constructor() {
let expression = `${AUTOFILL_TOKEN_BILLING} ${AUTOFILL_FIELD_NAME}`;
let model = new DynamicInputModel({
autoComplete: AutoFillUtils.validate(expression) ? expression : AUTOCOMPLETE_ON
//...
});
}
}Besides you can make user input more comfortable, providing HTML5 datalists
by setting the list property of DynamicInputControlModel:
new DynamicInputModel({
id: "basicInput",
label: "Example Input",
list: ["One", "Two", "Three", "Four", "Five"]
})Why should I give NG Dynamic Forms a try?
It will keep all your Angular forms highly maintainable and thus is probably going to save you a significant amount of time.
When should I use NG Dynamic Forms?
Whenever your Angular application is driven by several complex forms.
When should I not use NG Dynamic Forms?
Whenever you need to implement only simple forms or extremely individual form layouts / form control configurations.
Does NG Dynamic Forms support custom form controls?
No, not out of the box. You'd have to create your own UI package in order to achieve this.
Are there any other dynamic forms libraries for Angular?
Very few, namely ng-formly and angular-formio.
How can I support this project besides contributing issues or code?
Star the repository.
- Logo design made by oscarana