Skip to content
This repository has been archived by the owner on Sep 20, 2024. It is now read-only.

Settings: List difference between "saved" settings and current settings #2696

Closed
BigRoy opened this issue Feb 11, 2022 · 1 comment
Closed
Labels
community contribution type: feature Larger, user affecting changes and completely new things

Comments

@BigRoy
Copy link
Collaborator

BigRoy commented Feb 11, 2022

Feature

With the new 'versioned settings' from #2570 we can get the nice visual messages like:

"Your settings are loaded from an older version"

I was thinking it would be nice that in the case the user (or only for admins) is not sync that same bar shows an extra button to that will pop-up a little list widget showing the changes:

+ applications/additional_apps
- modules/ftrack
. modules

With:

  • + new key in the default settings
  • - removed key in new default settings compared to your previous settings
  • . changed value for an existing key -> especially nice if this could show old vs new value

Would be extra nice if clicking the names for any of the entries in the list would put the settings entity.path into the breadcrumb bar and actually directly move to it.

We should be able to compare with the stored settings in the database, right?

Notes

I'm not sure if . changed can happen automatically, but that's what I would expect when an enum has a valid value renamed or removed I'd assume the settings would automatically reset that to the new value in default settings.

Browsing to a - removed key of course couldn't be done. We could technically split on / until we find one that is currently valid using get_entity_from_path?

[cuID:OP-2624]

@MustafaJafar MustafaJafar added type: feature Larger, user affecting changes and completely new things community contribution labels Jul 7, 2023
@BigRoy
Copy link
Collaborator Author

BigRoy commented Jul 3, 2024

With AYON having a different settings front-end this has become irrelevant.

@BigRoy BigRoy closed this as completed Jul 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
community contribution type: feature Larger, user affecting changes and completely new things
Projects
None yet
Development

No branches or pull requests

2 participants