Severity: enhancement → major
OS: Other → All
Summary: [Compat Data] Switch to database-independant IDs → Switch to database-independant IDs
Whiteboard: [specification][type:feature] → [bc:infra][bc:milestone=bicycle]
The JSON API v1.0 spec has some requirements on using UUIDs in creating resources: http://jsonapi.org/format/1.0/#crud-creating-client-ids A 204 No Content response is allowed if the created resource matches the POSTed resource. For the v2 API, creating a resource also includes generating a historical link, so a 201 Created will always be returned.
To speed import, Feature resources should use MDN-generated UUIDs. This work is covered in bug 1246967. The sequence will be something like: - Add UUID fields to all resources, in addition to the database-generate fields. Generate UUIDs for resources other than features - MDN adds UUIDs to page API - An import process assigns MDN UUIDs to features representing pages - UUIDs are generated for the rest of the feature resources - The database ID is dropped and the UUID becomes the primary key
Depends on: 1246967
The BrowserCompat project is canceled. See https://github.com/mdn/browsercompat for current effort. Bulk status change includes the random word TEMPOTHRONE.
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.