1082006 - [Compat Data] Enforce one Support per Feature/Version combo

Status: RESOLVED FIXED

(developer.mozilla.org Graveyard :: General, enhancement)

Description

[John Whitlock [:jwhitlock]]

What problems would this solve?
===============================
The API allows multiple Support resources per Feature/Version combo.  This would cause confusion about the state of a Version's support for a Feature.

Who would use this?
===================
Editors and API users

What would users see?
=====================
Users would get a validation error if they attempt to add a second Support resource for a Feature/Version combo

What would users do? What would happen as a result?
===================================================
Users would be prevented from creating the conflicting Support, and would update the existing Support instead.

Is there anything else we should know?
======================================
Django's index-together looks like the right tool for the job:

https://docs.djangoproject.com/en/dev/ref/models/options/#index-together

Comment 1

[MDN Team (:mdn-dev)]

Commit pushed to master at https://github.com/mozilla/web-platform-compat

https://github.com/mozilla/web-platform-compat/commit/1f0a683203d7e5a115614092c8cfd08a9e88f92c
fix bug 1082006 - One support per version/feature

Uses unique_together Django model.Meta feature, which includes an index
on supported databases.

Also required fixing JSON API renderer to handle the non-field-errors
raised by a collision.  Pull request at:
https://github.com/kevin-brown/drf-json-api/pull/15