-
Notifications
You must be signed in to change notification settings - Fork 240
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
docs: typed policy engine DR #4526
Conversation
docs/developer/decision-records/2024-10-05-typed-policy-engine/README.md
Outdated
Show resolved
Hide resolved
docs/developer/decision-records/2024-10-05-typed-policy-engine/README.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's discuss this further. I don't like having two implementations of the policy engine and I also do not want to eliminate hierarchical scopes as they are useful.
- it makes no sense to have a function/validator bound to all the scopes, scopes have well defined bound, they could | ||
share context content (e.g. `Instant now` field could be one of them), but this should happen at the `PolicyContext` | ||
hierarchy level. | ||
- scope hierarchy won't be a thing anymore (e.g. `scope` and `scope.child`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is used. Let's discuss this
@jimmarino @paullatzelsperger I revisited the DR scope, now is more narrow and it will permit to keep scopes hierarchy. |
@jimmarino DR is ready to review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
What this PR changes/adds
Adds DR for typed policy engine refactor
Why it does that
Briefly state why the change was necessary.
Further notes
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method
signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
Linked Issue(s)
Part of #3511
Please be sure to take a look at the contributing guidelines and our etiquette for pull requests.