Conversation
Generated with schemer.py script. One changes needed for some objects.
jessepeterson
left a comment
jessepeterson
left a comment
There was a problem hiding this comment.
This is so cool! I love the idea of regularly scraping the page. Sometime in the past Apple had a developer document "diff" tool - you could compare documentation changes between versions. I think they got rid of that the last WWDC cycle or two, not sure.
Anyway but NOT having to manually keep track of changes sounds great!
Couple notes/interesting bits/questions:
- How do the "sub" documents get handled? I don't see them here.
- How would a "diff" look against the existing docs? How do we preserve manually created items?
- How should resources that are obviously shared between the two repos (ABM and ASM) be handled? Symlinks? A shared "axm" folder (where only each individual folder would have the unique things just for it).
But neat none-the-less! Even if all of the above didn't work just seeing the diffs generated regularly would be helpful for tracking changes in case a field or structure is added or whatever!
Thanks!
| "properties": { | ||
| "errors": { | ||
| "description": "An array of one or more errors.", | ||
| "$ref": "[errorresponse.errors].json" |
There was a problem hiding this comment.
I don't see this file in the PR. But even if it were you can see what I did in this commit here where I put the sub-documents for any given "root-level" document inside of the parent doc:
This keeps the proliferation of json documents somewhat manageable.
2 participants
Generated with schemer.py script. One-off changes needed for some objects. Just so you can see what the general output is like.