Removing autosave functionality (not in use)

[olemartinorg]

Description

Removing the autoSave toggle. My reasons for this is:

• You have to know what you're doing to toggle it off, because it isn't documented anywhere (you had to read our code to find it).
• Nobody is using this setting, as far as I can tell (and I've downloaded every app currently in production and every app I could get a hold of that's on tt02).
• Server-side calculations stop being responsive if you toggle it off.
• There's been a notice in our code for a while asking if that setting is used at all, and everyone had to code around it hoping other changes to form saving didn't break this unknown feature.
• If you try to enable it, you might find that we only respect the setting from the last layout file we processed, so it would've been best to set it on every single layout file if you really wanted it. Or just never change the page order.
• We have no tests for it, so nobody knows if it works in conjunction with other features (such as triggers for components, seem to just not be working at all).
• Nobody seem to have requested it (it was implemented in Feature/4778 multiple form pages app altinn-studio#4953, which links to two issues that never describes anything about enabling/disabling auto-saving). Either that, or this is leftovers from the past, if no autosaving used to be the default until this was introduced.
• I don't want to support it in Experiment: Storing the data model in a Context #1175.

A recording of it action, for posterity. Notice how server-side calculations are not updated until you manually trigger a save.

recording-no-autosave.mp4

Related Issue(s)

• Experiment: Storing the data model in a Context #1175

Verification/QA

• Manual functionality testing
  • I have tested these changes manually
  • Creator of the original issue (or service owner) has been contacted for manual testing (or will be contacted when released in alpha)
  • No testing done/necessary
• Automated tests
  • Unit test(s) have been added/updated
  • Cypress E2E test(s) have been added/updated
  • No automatic tests are needed here (no functional changes/additions)
  • I want someone to help me make some tests
• UU/WCAG (follow these guidelines until we have our own)
  • I have tested with a screen reader/keyboard navigation/automated wcag validator
  • No testing done/necessary (no DOM/visual changes)
  • I want someone to help me perform accessibility testing
• User documentation @ altinn-studio-docs
  • Has been added/updated
    • Cleaning up (removing text for autoSave, evalExpression) altinn-studio-docs#955
  • No functionality has been changed/added, so no documentation is needed
  • I will do that later/have created an issue
• Changes/additions to component properties
  • Changes are reflected in both src/layout/layout.d.ts and layout.schema.v1.json, and these are all backwards-compatible
  • No changes made
• Support in Altinn Studio
  • Issue(s) created for support in Studio
  • This change/feature does not require any changes to Altinn Studio
• Sprint board
  • The original issue (or this PR itself) has been added to the Team Apps project and to the current sprint board
  • I don't have permissions to do that, please help me out
• Labels
  • I have added a kind/* label to this PR for proper release notes grouping
  • I don't have permissions to add labels, please help me out

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
1 Code Smell

37.5% Coverage
0.0% Duplication

[bjosttveit]

Enig, få det bort