Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FluentValidation Rules #32

Open
Tecorey opened this issue Sep 9, 2023 · 3 comments
Open

FluentValidation Rules #32

Tecorey opened this issue Sep 9, 2023 · 3 comments

Comments

@Tecorey
Copy link

Tecorey commented Sep 9, 2023

Thank you for your open-source library, which has helped me solve many issues in my project. I use FluentValidation extensively in my work, especially its rules that may be used in multiple places. Can we utilize FluentValidation's rules with this library?

@pglazkov
Copy link
Owner

Thank you for your feedback, glad you found this library to be useful.
Regarding your question, I don't think this is possible at the moment, at least this is not a scenario I tested or encountered before. It seems like these two libraries serve almost the same purpose and not meant to be used together. Or maybe I'm not understanding your use case. Maybe you could elaborate a bit, how would you like to use the two libraries together?

@Tecorey
Copy link
Author

Tecorey commented Sep 12, 2023

Like this
https://github.com/GrantByrne/DeadSimpleWpfFluentValidation.git
Or
https://github.com/dotnet9/FluentValidationForWPF.git
They implement similar functions to yours, but they are not easy to use.

@pglazkov
Copy link
Owner

It looks like what you are looking for an implementation of INotifyDataErrorInfo, similar to NotifyDataErrorInfoAdapter.cs, but for FluentValidation. You can try to implement it yourself based on the code from the repos that you mentioned or raise an issue in FluentValidation repo, maybe they can add it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants