Snaterlicious added a subscriber: Snaterlicious. Snaterlicious added a comment.
While trying to compile some high-level documentation, I figured out that that does not make much sense without some proper visualization. Consequently, I started drawing out the data model as that is the component where basically all of the terms "derive" from. The original intention was to not go into too much of detail -- then again, how to avoid? Working on high-level documentation requires having an overview first. Currently there is no way to get the complete picture without crawling through all the code and doxygen diagrams do not really provide useful. For high-level documentation (i.e. https://phabricator.wikimedia.org/T75603), the diagram should be stripped down considerably. Nonetheless, overall documentation would benefit a lot from having and maintaining that detailed view on the core component. Please feel free to review the diagram, I would really like to get the picture right: F42947: DataModel.png <https://phabricator.wikimedia.org/F42947> TASK DETAIL https://phabricator.wikimedia.org/T75604 REPLY HANDLER ACTIONS Reply to comment or attach files, or !close, !claim, !unsubscribe or !assign <username>. EMAIL PREFERENCES https://phabricator.wikimedia.org/settings/panel/emailpreferences/ To: Snaterlicious Cc: Snaterlicious, JeroenDeDauw, JanZerebecki, Lydia_Pintscher, daniel, Wikidata-bugs, Jdouglas, aude _______________________________________________ Wikidata-bugs mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikidata-bugs
