[x] I documented the TypeScript code using JSDoc style.
[x] I added multiple screenshots/screencasts of my UI changes
[x] I translated all the newly inserted strings into German and English
Motivation and Context
I was working on integrating Apollon v3 with Artemis, and realised that sometimes v2 models are stored with the wrong format, which causes errors when Apollon 3 tries to load them and convert them to v3 schema.
Description
It can happen that v2 models are stored with the wrong format / typing, which will cause errors to be thrown by the backwards compatibility code that tries to convert the corrupt v2 model to v3. For example, essential fields of the model might be absent (e.g. elements, assessments, etc) or of the wrong type (e.g. an empty object instead of an array).
Steps for Testing
Basically create a corrupted JSON diagram.
Run locally (npm start)
Create and save the diagram
Corrupt the diagram: open developer console on browser and type the following:
Checklist
Motivation and Context
I was working on integrating Apollon v3 with Artemis, and realised that sometimes v2 models are stored with the wrong format, which causes errors when Apollon 3 tries to load them and convert them to v3 schema.
Description
It can happen that v2 models are stored with the wrong format / typing, which will cause errors to be thrown by the backwards compatibility code that tries to convert the corrupt v2 model to v3. For example, essential fields of the model might be absent (e.g.
elements,assessments, etc) or of the wrong type (e.g. an empty object instead of an array).Steps for Testing
Basically create a corrupted JSON diagram.
npm start)Test Coverage