Abdellatif Ait boudad

@Zdenalus postponed to `v6` due to some limitation, you can implement a close approach using a custom extension, here are some extensions that you may check to have an idea:...

I would like to introduce a pipe which could be used in a such case instead

> Thank you for your amazing work! We saved a lot of time thank to this library Awesome, happy to hear that 👍 > I wonder if it's already implemented....

> Is this on the roadmap? yes

> I'm willing to try and implement this feature myself and submit a PR All validators are wrapped within the following function [field-validation.ts#L126](https://github.com/ngx-formly/ngx-formly/blob/main/src/core/src/lib/extensions/field-validation/field-validation.ts#L126) so adding just an extra check would...

After re-checking, I see the need of a such feature. This will fix the following issue https://github.com/ngx-formly/ngx-formly/issues/2385 as well. So I'm open to any good proposal form your side :pray:!

just go ahead with your solution I may see if it can solve the mentioned issue as well, my thought was with `showValidation` you can have a full control of...

> Makes sense, but do you want to replace the current way using the `FormlyModule` or just add another way? For now just add another way, later we may deprecate...

> Also, is there anything I can do about the failing tests? I can't see the netflify logs so no idea what's going on there... Not related to this issue...

Could you please update the preset section as well https://github.com/ngx-formly/ngx-formly/blob/main/docs/formly-field-presets.md#defining-a-preset