We need to update the documentation of our js data model to reflect
reality again.
Version: master
Severity: normal
Whiteboard: u=dev c=frontend p=0
We need to update the documentation of our js data model to reflect
reality again.
Version: master
Severity: normal
Whiteboard: u=dev c=frontend p=0
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | None | T75606 update documentation of js data model | |||
Invalid | daniel | T75603 [Story] update documentation of high-level data model | |||
Invalid | None | T96587 [Task] The data model specification should cover the notion of alias IDs (redirects) | |||
Invalid | None | T98598 [Story] Overhaul documentation of data values | |||
Invalid | None | T96679 [Task] Put sources of datamodel diagrams into the respective code repositories | |||
Invalid | None | T96681 [Task] Review and polish new version of data model primer |
This ticket needs some more specification. I am not sure about what the expected outcome should be as I do not see the need for the ticket to be blocked by the high-level documentation.
The diagram embedded on https://github.com/wmde/WikibaseDataModelJavaScript does reflect the current state of the JS data model and proofs to be very useful already.
After merging https://github.com/wmde/WikibaseDataModelJavaScript/pull/20, it will be possible to generate a proper code documentation with JSDuck.
That should be fair enough regarding JS data model specific documentation.