Closed Bug 1063148 Opened 11 years ago Closed 11 years ago

[Compat Data] Add specification sections to compat data store

Categories

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

All
Other
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jwhitlock, Unassigned)

References

Details

(Whiteboard: [specification][type:feature])

What problems would this solve? =============================== Specification sections appear with compatibility data, and are often referenced. This generalizes the concept so individual features can be referenced. Who would use this? =================== Developers looking for the standard for a feature What would users see? ===================== The name of and link to the exact section of a spec What would users do? What would happen as a result? =================================================== A developer would be able to jump to the relevant portion of the spec for a given feature Is there anything else we should know? ====================================== Draft API docs at http://web-platform-compat.readthedocs.org/en/latest/draft/resources.html#specifications-sections
Blocks: 996570
Severity: normal → enhancement
Commits pushed to master at https://github.com/mozilla/web-platform-compat https://github.com/mozilla/web-platform-compat/commit/92e959a1d275e5138977d29810dd8163f5ae3f1e bug 1063148 - Add specification sections https://github.com/mozilla/web-platform-compat/commit/d4fdc21ed7f6d8d3cb766e5a7c7b63f57d876ec0 bug 1063148 - Add sections to feature A lot of gymnastics to avoid addining a M2M instance to the API: - feature.sections is an ordered PK list - historicalfeature.sections is a JSONfield list - A m2mchanged signal is used to keep the cache up-to-date https://github.com/mozilla/web-platform-compat/commit/c1fcb062025c3125ad1d3edf20f2a40a7c84995b bug 1063148 - Add sections.features links https://github.com/mozilla/web-platform-compat/commit/0eb147db505056053b2df0fcc109295a09e71134 fix bug 1063148 - Add optional sections.number TranslatedField due to differences in section number across languages
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.