Issue #3846
closed
- Triaged changed from No to Yes
- Sprint set to Sprint 39
FYI, there are a bunch of other models that have similar unique constraints: publishers, remotes, exporters, distributions, users, artifacts.
According to the django-rest-framework issue tracker on Github (4509, 5385, ...) it looks like we're not the first to deal with this problem. If I understand it right, collaborators don't have any interest in tackling it themselves or their point of view is that 400 is OK for uniqueness constraints. So I guess we'll have to deal with it by implementing our own subclass of ApiException.
- Status changed from NEW to ASSIGNED
- Assignee set to vdusek
- Sprint changed from Sprint 39 to Sprint 40
- Status changed from ASSIGNED to POST
- Sprint changed from Sprint 40 to Sprint 41
- Sprint changed from Sprint 41 to Sprint 42
- Status changed from POST to CLOSED - WONTFIX
Based on the reaction of upstream and discussion on the PR.
- Sprint/Milestone set to 3.0.0
We are removing the 'API' category per open floor discussion June 16, 2020.
Also available in: Atom
PDF