-
-
Notifications
You must be signed in to change notification settings - Fork 407
TextSeparator = ", " for concatenating errors #2925
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
Labels
Comments
It seems like something someone could set, and perhaps the default should be |
Freelancingonupwork
added a commit
to Freelancingonupwork/csla
that referenced
this issue
May 15, 2024
…ing-errors/main
rockfordlhotka
added a commit
to Freelancingonupwork/csla
that referenced
this issue
May 17, 2024
…ing-errors/main
rockfordlhotka
added a commit
to Freelancingonupwork/csla
that referenced
this issue
May 20, 2024
…ing-errors/main
rockfordlhotka
added a commit
that referenced
this issue
May 20, 2024
* Add DisplayIndex Property to Business Rules * Test * Update * Text separator for concatenating errors * Chnages --------- Co-authored-by: Stefan Ossendorf <[email protected]> Co-authored-by: Mayur Kasidariya <[email protected]> Co-authored-by: Rockford Lhotka <[email protected]>
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The standard validation error messages such as
[Required]
are proper sentences ending with a.
and I think this is good practice.Csla.Blazor.PropertyInfo
assumes error messages won't end with a.
using", "
to concatenate errors, so you end up with:Should
TextSeparator = " "
or perhaps be apublic static string TextSeparator { get; set; }
instead?The text was updated successfully, but these errors were encountered: