The use case is supporting the creation of sequences from seq.json files. The files will have their json contents stored as strings in postgres, but the seqN.txt variant will be uninitialized. If the sequence.json input conforms to the schema, the SeqN.txt that is written out needs to round trip to identical sequence.json ignoring whitespace which is not syntactically meaningful in JSON.
Steps
Load and Gos
Immediate Commands
Hardware Commands
Seq IDs
Block Statements (requires adaptation code)
Loads
Activates
Ground Events
Metadata (may need more discussion once we have examples)
The use case is supporting the creation of sequences from seq.json files. The files will have their json contents stored as strings in postgres, but the seqN.txt variant will be uninitialized. If the sequence.json input conforms to the schema, the SeqN.txt that is written out needs to round trip to identical sequence.json ignoring whitespace which is not syntactically meaningful in JSON.