Fix Dataset Configurations

[youri-k]

URL of deployed dev instance (used for testing):

• https://___.webknossos.xyz

Steps to test:

• open Dataset in View Mode and change segmentation settings (e.g. opacity)
• open Volume tracing without fallback on the same dataset and change volume layer settings (e.g. opacity)
• reopen Dataset in View Mode => segmentation settings should persist
• reopen tracing => volume layer settings should persist

Issues:

• fixes Volume layer opacity does not persist #4650

---

• Updated (unreleased) changelog
• Updated (unreleased) migration guide if applicable
• Updated documentation if applicable
• [ ] Adapted wk-connect if datastore API changes
• [ ] Needs datastore update after deployment
• Ready for review

[fm3]

Backend looks good to me, I think this is a clean solution :) I just added a few minor comments.

[philippotto]

Great stuff! Also kudos for cleaning up the obsolete quality-setting and fighting through the front-end tests :)

I'm just a bit unclear about why it is necessary to send the dataset layers to the back-end when requesting the settings. Since the volume-vs-fallback-layer-specific logic is now duplicated, I'd prefer to refactor this a bit. See my other comment for context/details :)

[philippotto]

Excellent :)

[youri-k]

@fm3 Could you have a look at the backend again after the newest frontend changes. I don't know how to feel about the abstraction level in the ConfigurationController.

[youri-k]

ToDo:

• migration for defaultConfiguration in DataSet
• reversions for complete evolution
• fix e2e tests
• write additional tests for new schema

[fm3]

Backend LGTM, great work 🎉 Thanks for going through all the renamings :) I think it is a lot more clear and consistent now

[philippotto]

Awesome! Great job making this beautiful 👍 See my two comments about validation + nesting, though :)

[philippotto]

Awesome! Looking forward to seeing this merged :)