Daniele Pecora

As I see, empty fields are not handled as invalid inputs if they are required. An exception is made for 1st level children. For all nested fields the parent container...

> So this is the intended behavior then? What puzzles me a bit is that if one of the other nested properties is not empty (for example, typing something for...

> Question 1: would be nice to have required working as expected, so how is it possible? **Answer** Create a custom schema validator that corrects the error message path, so...

@JianhuisHuang We worked around this by using a custom validator factory, which does take in count if an optional field is empty. Here is how we use it: https://github.com/daniele-pecora/ngx-schema-form-widgets-material/blob/master/projects/ngx-schema-form-widgets-material/src/lib/fix-optional-empty-fields-z-schema-validator-factory.ts

Here you go: In this [example at stackblitz](https://stackblitz.com/edit/ngx-schema-form-customs) you will find a button `Re-render form` at bottom.

You may have a look at [this/my extension](https://github.com/daniele-pecora/ngx-schema-form-view/) on how to remap your model to the data structure required by the backend.

Unfortunately `enum` contained in `oneOf` of a `visibleIf` condition will not be processed for visibility. But this could be handelt inside the validator. Here a quick and dirty example that...

The widget library **[ngx-schema-form-widgets-material](https://github.com/daniele-pecora/ngx-schema-form-widgets-material)** based on Google Material Design contains a `Wizard` widget that might do what you need here. You may have a look at the demo page [click...

@aahventures you might look into the source code folder `_forms/...`

### What I found out so far When referencing from inside an array item currently only relative path do work. e.g `container1/enabler` `enabler` In the example inside `container2` : **What...