Daniele Pecora

This is deeply related to the issue #233 . We already resumed that the binding MUST be done with `[(ngModel)]` because of the buit-in emitter. See also: https://github.com/guillotinaweb/ngx-schema-form/issues/233#issuecomment-420704459

Could you provide an example on [Stackblitz](https://stackblitz.com/)?

**Question** 1. Can I bind all the fields without explicitly specifying the path? Something like a wildcard bind, **Answer** No you can't unless you specify a validator for every property...

@aahventures I would provide a custom `SchemaValidatorFactory` which would be used in the UI Editor (See doc for details). The implementation of the `SchemaValidatorFactory` simply contains no validation at all....

@aahventures Probably 😁

## Idea of a solution Often the JSON schema used as base for the form will be provided by a REST web-service endpoint. Therefore it doesn't always have the final...

That is true, but how could it be handled otherwise and maintain the required validation?

Partially it does, because `required` wouldn't trigger if field is empty, only triggers if field is not present.

ngx-schema-form doesn't rely on angular form control validation rather on a json schema validator. The default validator implementation is Z-Schema. JSON Schema validation counts an empty property as present and...

I don't know it myself. For preventing a huge breaking change this should end in a feature that can optionally be activated. Maybe via `forRoot(...)` or smt else