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

"Port" the unique rule from Eve? #539

Closed
funkyfuture opened this issue May 10, 2020 · 2 comments
Closed

"Port" the unique rule from Eve? #539

funkyfuture opened this issue May 10, 2020 · 2 comments

Comments

@funkyfuture
Copy link
Member

we should do that, or shouldn't we?

i can think of two different semantics atm:

  • simply that any container like lists can contain only one instance of a value
  • the more tricky one where a sequence of mappings must not have one value assigned to the same field among these mappings

maybe that would be two different rules to avoid ambiguity and to keep the code straight-forward.

the Cerberus implementation should hence be capable to solve Eve's limitation of not detecting duplicates in a payload. while Eve would need to extend it with regards to the database collection.

@nicolaiarocci
Copy link
Member

Of course I'd like this 😃 I also agree on having two different rules: they solve (not-so-)slightly different problems.

@funkyfuture
Copy link
Member Author

closing this issue as there are currently no intentions to continue a next major release.

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

No branches or pull requests

2 participants