We should support auto saving of the data model when editing

[lorang92]

Description

We should support auto saving of the data model when editing in our new tool. The current implementation forces the user to hit save which is easy to forget and causes loss of data if the user closes the tab or leaves unintentionaly.

Considerations

• Could we save the json schema withouth generation c#, metadata and xsd files?
  • When should these be generated? Push to repo?
• Could Local storage solve some of the issues? Combination of the two?

Ops requirements

Are there any requirements for monitoring? What is being built and what could go wrong? Are there any requirements related to backup?

Acceptance criteria

• The json schema is auto saved when editing
• We have a sure way that necessary files are generated from json schema (probably not on every save)

Specification tasks

• [ ] Development tasks are defined

Development tasks

Add tasks here

Test

Add test cases here as checkboxes that are being tested as part of the changes.

Definition of done

Verify that this issue meets DoD (Only for project members) before closing.

• [ ] Documentation is updated (if relevant)
  • [ ] Technical documentation (docs.altinn.studio)
  • [ ] User documentation (altinn.github.io/docs)
• [ ] QA
• [ ] Manual test is complete (if relevant)
• [ ] Automated test is implemented (if relevant)
• [ ] All tasks in this userstory are closed (i.e. remaining tasks are moved to other user stories or marked obsolete)

[ivarne]

An alternative/additional improvement would be to persist the changes in LocalStorage so that even in the event of network failure you can recover changes.