-
Notifications
You must be signed in to change notification settings - Fork 9
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: ADR on spend-limit constraint #523
Conversation
e5a3bbb
to
a36d826
Compare
a36d826
to
3c39b29
Compare
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.
LGTM. One minor suggestion might be to include link to this ADR here in the list of other ADRs (though it does look like the more recent ones are missing from the list).
* Policy A, an ``active`` policy with a ``spend_limit`` of 10,000 | ||
* Policy B, an ``active`` policy with a ``spend_limit`` of 40,000 | ||
* If Policy A were set to ``!active`` | ||
* Policy B's ``spend_limit`` can now be set to ``50,000`` (even if spend has occured on Policy A or B) |
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.
super nit: doesn't seem like other instances of numeric dollar values here (e.g., 10,000
and 40,000
above) are formatted with the backticks. could remove the backticks for consistency with other numeric values.
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.
Updated in this PR 👍🏽
#528
ADR on the recently introduced
spend-limit
constraint within theclean()
function within thesubsidy_access_policy
modelDescription:
Add a description of your changes here.
Jira:
ENT-XXXX
Merge checklist:
./manage.py makemigrations
has been runPost merge: