You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The wolverine FluentHttp library currently registers fluent validators as singleton. This prevents the use of translated error messages and potential other usage of scoped/transient resources within the validators.
Describe the solution you'd like
I think the best solution would to have the options to pass the lifetime on 'UseFluentValidationProblemDetailMiddleware' with singleton as default value. Next to that an attribute can be added to modify the scope of a single validator.
The text was updated successfully, but these errors were encountered:
That's not 100% accurate. Wolverine registers validators as singletons if there are no constructors with arguments by default, and any concrete validators with dependencies as Scoped
Is your feature request related to a problem? Please describe.
The wolverine FluentHttp library currently registers fluent validators as singleton. This prevents the use of translated error messages and potential other usage of scoped/transient resources within the validators.
Describe the solution you'd like
I think the best solution would to have the options to pass the lifetime on 'UseFluentValidationProblemDetailMiddleware' with singleton as default value. Next to that an attribute can be added to modify the scope of a single validator.
The text was updated successfully, but these errors were encountered: