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
Using the code from #205, we experience serious performance issues, making this package unusable for us.
We have hundreds of fields in our model with lists of more complex models. Because our form is user-configurable, we have effectively a tree of those complex models. We suspect the performance of PropertyPathHelper.ToFluentPropertyPath to be the problem.
We use this package since 2021 and had never issues with the default MemberNameValidatorSelector.
Concerning the original issue from #204, I think there should be a better way to select the validator of the root model, if needed. It should at least be configurable, as for our project, the previous selection strategy worked better.
It seems like a difficult problem, though, considering #235, #76, and #104.
The text was updated successfully, but these errors were encountered:
Using the code from #205, we experience serious performance issues, making this package unusable for us.
We have hundreds of fields in our model with lists of more complex models. Because our form is user-configurable, we have effectively a tree of those complex models. We suspect the performance of
PropertyPathHelper.ToFluentPropertyPath
to be the problem.We use this package since 2021 and had never issues with the default MemberNameValidatorSelector.
Concerning the original issue from #204, I think there should be a better way to select the validator of the root model, if needed. It should at least be configurable, as for our project, the previous selection strategy worked better.
It seems like a difficult problem, though, considering #235, #76, and #104.
The text was updated successfully, but these errors were encountered: