What problem does this feature solve?
With the current implementation, the Angular library injects a ValidationService at init time. This can be overridden with a custom validation service, but there is no way to deactivate it in case the user wishes to do so.
What does the proposed API look like?
Similar to #367 the idea is to add a setting to the library to allow disabling this service.
This seems to be the only way to achieve the goal since changing the way undefined are handled at init time might break installations. This would allow a gradual migration path
What problem does this feature solve?
With the current implementation, the Angular library injects a
ValidationServiceat init time. This can be overridden with a custom validation service, but there is no way to deactivate it in case the user wishes to do so.What does the proposed API look like?
Similar to #367 the idea is to add a setting to the library to allow disabling this service.
This seems to be the only way to achieve the goal since changing the way undefined are handled at init time might break installations. This would allow a gradual migration path