Store JSON for things, collections, and user designs #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Greetings,
I am looking at offline archiving my collections and designs from thingiverse, juuust in case, given its current state. To this end, I've started adding basic support for dumping the raw JSON details for things, collections, and the list of user designs. My hope is that sometime down the line this can be used by an importer to mediagoblin or something similar, or otherwise post-processed.
For now, it just unconditionally dumps the JSON (and doesn't do any checks for API errors to make sure it's actually returning the requested information), and dumps to "thing:$id.json", "collection:$id.json", or "designs:$username.json" mirroring how thingiverse labels them.
If this looks OK as a first pass, I was going to add some error checking code in the Grouping. If this looks OK generally, do you think it should be controlled with an argument? something like "--dump-json={all,designs,thing,collection}" maybe.