Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change seqvars/factory default presets strategy #1920

Closed
holtgrewe opened this issue Aug 22, 2024 · 0 comments · Fixed by #2067
Closed

Change seqvars/factory default presets strategy #1920

holtgrewe opened this issue Aug 22, 2024 · 0 comments · Fixed by #2067
Assignees
Labels
enhancement New feature or request

Comments

@holtgrewe
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
We currently use "model clusters" library to create the factory default presets in memory only. This appeared to be a good idea as long as there were only presets and no queries. However, now we can - of course - not create foreign keys to these in memory objects 🤦.

Describe the solution you'd like

  • introduce a "is factory default" boolean flag, defaulting to false and not modifiable through REST API
  • create an on-startup handler that creates the presets in memory and syncs them to the database (UUIDs will remain stable)
  • adjust the code for the factory defaults to use the "is factory default" boolean flag

Describe alternatives you've considered
For now, the factory defaults must be explicitely copied to per-project user modifiable presets.

Additional context
N/A

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant