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
{{ message }}
This repository has been archived by the owner on Jun 5, 2020. It is now read-only.
I had an idea. Might be good, might be bad, I thought I'd float it out here and see what people think.
The idea is that writing a rule today usually means creating a constructor and adding items to the input properties collection. Which is ok, but not declarative. Also, there's not a good way to reference values from other parts of the object graph - ancestors, siblings, or children of the target object.
I don't have this clearly in my head - but it occurred to me that XAML data binding has mechanisms for binding to ancestors at least. Maybe there's some way to make life better?
I like this approach, it would open all kinds of doors to implement business rules that could access any property in the object graph, exciting times to be a software develoepr :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I had an idea. Might be good, might be bad, I thought I'd float it out here and see what people think.
The idea is that writing a rule today usually means creating a constructor and adding items to the input properties collection. Which is ok, but not declarative. Also, there's not a good way to reference values from other parts of the object graph - ancestors, siblings, or children of the target object.
I don't have this clearly in my head - but it occurred to me that XAML data binding has mechanisms for binding to ancestors at least. Maybe there's some way to make life better?
This is pretty vague - what do you think though?
The text was updated successfully, but these errors were encountered: