Design #162
closedRevisions to the JSON output (incl to some fields and field names)
0%
Description
I stepped through the JSON output from RuleMaker for a sample rule, and compared it line by line with the specification, as well as with some earlier and more recent documentation. And I thought a few things through a little more.
Hers is a sample .json file with the new elements.
https://gitlab.com/xalgorithms-alliance/data-with-direction-specification/dwds-documents/-/blob/master/current/sample-dwds-output.json
Rather than giveng you a git diff, here is an etherpad that shows in two colours the changes and my comments with easier visualization:
https://etherpad.wikimedia.org/p/xalgorithms30
There are a few minor syntax glitches in my sample json -- I am not sure what the errors are.
Let me know if there's a preference to schedule a call.
Files
Updated by Joseph Potvin over 1 year ago
- Priority changed from Normal to High
I switched this to 'high' because for examples to be re-used, any adjustments to the JSON file will need to be done first.
Updated by Joseph Potvin over 1 year ago
- File TEST-DATA-TO-TRACK-FIELDS_ADJUSTED3_rule_d5ab3144-4117-4d55-b1c0-fcac50123dc5.json TEST-DATA-TO-TRACK-FIELDS_ADJUSTED3_rule_d5ab3144-4117-4d55-b1c0-fcac50123dc5.json added
- Priority changed from High to Urgent
Hi, Thanks for all the changes. I did a new thorough line-by-line test of the current https://rulemaker3-dev.onrender.com export, and have the following suggestions (in orange):
https://etherpad.wikimedia.org/p/xalgorithms31
My current export test file is attached here.