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

Provide more details about the rule in the BrokenRule type #3224

Closed
rockfordlhotka opened this issue Dec 13, 2022 · 0 comments · Fixed by #3945
Closed

Provide more details about the rule in the BrokenRule type #3224

rockfordlhotka opened this issue Dec 13, 2022 · 0 comments · Fixed by #3945

Comments

@rockfordlhotka
Copy link
Member

rockfordlhotka commented Dec 13, 2022

I don't think we'll do number 1, as this is something that can be solve by a LINQ query - were the BrokenRule type to provide more details about the broken rule.

For number 2, It might be that the simplest solution is to have the BrokenRule class expose a property so the actual underlying IBusinessRule object is available.


I would like to make a couple of suggestions for the next version of Csla

  1. We could add 'GetFirstBrokenRules()' in BrokenRulesCollection, this method will return 'first' broken rules for the object (or object graph).
  2. Add Priority to BrokenRule.

Kind Regards

Originally posted by @Chicagoan2016 in #3222 (reply in thread)

Freelancingonupwork added a commit to Freelancingonupwork/csla that referenced this issue May 16, 2024
StefanOssendorf added a commit to Freelancingonupwork/csla that referenced this issue May 18, 2024
StefanOssendorf added a commit to Freelancingonupwork/csla that referenced this issue May 20, 2024
StefanOssendorf added a commit to Freelancingonupwork/csla that referenced this issue May 21, 2024
StefanOssendorf added a commit to Freelancingonupwork/csla that referenced this issue May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Development

Successfully merging a pull request may close this issue.

3 participants