- Edited
Force export even when 'export' is unchecked?
We have a lot of .spine files that contain references that we normally don't want exported, so we've been using the "disabling export" feature described here: Export - Spine User Guide: Disabling export
However: now we want to do a mass process of:
- export the .spine file to .json
- do an automated change to the .json data
- reimport the .json back to a .spine file
and I've realised that, doing this will mean that all of the skeletons set not to export, will be lost. And since operating on an exported .json is the only way to do mass automated work on .spine files, there's no way to change this data in a mass automated way; it will already be lost before my script can touch it. Is there a way to force the CLI to export ALL skeletons in a file, explicitly IGNORING the "export" checkbox?
There's not currently, unchecking export means it will never be exported. Your use case seems reasonable though. We'll add a setting in the next 4.1 beta. It'll be forceAll: true
in the export settings JSON, unless you have a better name.
Wonderful, thank you! As I mentioned in my other thread, I've worked around this with {ignore:true}
for now, so I won't need this at the moment after all, but I will probably wind up using it for something at some point, so thank you in advance!