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

Allow wildcard in call to SetRulesetForClientsideMessages #1912

Closed
danielgreen opened this issue Mar 9, 2022 · 4 comments
Closed

Allow wildcard in call to SetRulesetForClientsideMessages #1912

danielgreen opened this issue Mar 9, 2022 · 4 comments
Milestone

Comments

@danielgreen
Copy link
Contributor

danielgreen commented Mar 9, 2022

Is your feature request related to a problem? Please describe.

When calling SetRulesetForClientsideMessages I need to pass all the ruleset names, when it would be simpler to pass "*" as a wildcard. This already works for IncludeRuleSets I believe.

Describe the solution you'd like

A call to HttpContext.SetRulesetForClientsideMessages("*") should mean that all rules (whether in a ruleset or not) should be used to generate client-side validation attributes.

(Hopefully this isn't user error on my part - apologies if so!)

@JeremySkinner
Copy link
Member

Good idea, I think that'd be a useful change. Will aim to get this into the next release.

@JeremySkinner
Copy link
Member

10.4 has been pushed to nuget with this change.

@danielgreen
Copy link
Contributor Author

@JeremySkinner Thanks for pushing that out so quickly. Should it be added to the docs on here as well https://docs.fluentvalidation.net/en/latest/aspnet.html

@JeremySkinner
Copy link
Member

Could you open a PR to add it? Thanks!

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 26, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants