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.

Sign up for GitHub

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

Jump to bottom

Discuss whether or not an ARP may define a policy for a single attribute multiple times, and adjust AttributeReleasePolicy VO accordingly #1769

Open

phavekes opened this issue Nov 29, 2024 · 1 comment

Labels

Imported needs-input tech-debt

Member

phavekes commented Nov 29, 2024

This issue is imported from pivotal - Originaly created at Mar 8, 2016 by Daan van Renterghem

This could be tackled in the new ARP VO. For now it is backwards compatible thus not eagerly checking whether or not a policy has already been defined for an attribute.

Several options:

if a second policy is discovered, it is merged with the first
as is now: the first policy defined is the policy used
throw an error when adding a policy for an attribute that already as a policy defined.

The text was updated successfully, but these errors were encountered:

phavekes added Imported needs-input tech-debt labels

phavekes self-assigned this

Member Author

phavekes commented Nov 29, 2024

Unclear to me what the goal/value is of this story. (Thijs Kinkhorst - Sep 11, 2019)

phavekes removed their assignment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment