You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm frustrated when I make a small change to a mission model, and the simulation configuration templates I created for previous versions don't apply even though the sim configuration parameters haven't changed at all.
I could use aerie-cli or hasura to download and upload templates, but that's often more painful than re-creating the templates manually (which can be error prone).
Describe the feature request
I want my templates to be there when I add a new mission model, and even if I change the sim configuration, there's a common sense way to automatically migrate them to fit as best as possible. If the parameters are different from the last mission model (or all mission models), there could be some threshold of mismatches where the user is asked to specify whether or not to migrate some smartly selected set of templates.
But, as long as it is smart, maybe bugging the user is unnecessary because you can make all of them accessible, as discussed below.
There could be a problem where the server has many templates from many users, so including all of those in a dropdown for every user and every mission model could be problematic. Maybe a pattern for how other things are shared can be used (like for sharing scheduling goals). Forgetting how those are done, I could imagine that templates could be grouped by
those applied to the current mission model,
those for other mission models,
for the current user, and
for all users.
So, when a user selects the template drop-down, they see those from group 1, and they can open up other groups somehow.
There are many ways this might be done. Feedback from this feature's requestors, Maggie Mende or Brad Clement, will be happily given.
The text was updated successfully, but these errors were encountered:
Checked for duplicates
Yes - I've already checked
Alternatives considered
Yes - and alternatives don't suffice
Related problems
I'm frustrated when I make a small change to a mission model, and the simulation configuration templates I created for previous versions don't apply even though the sim configuration parameters haven't changed at all.
I could use aerie-cli or hasura to download and upload templates, but that's often more painful than re-creating the templates manually (which can be error prone).
Describe the feature request
I want my templates to be there when I add a new mission model, and even if I change the sim configuration, there's a common sense way to automatically migrate them to fit as best as possible. If the parameters are different from the last mission model (or all mission models), there could be some threshold of mismatches where the user is asked to specify whether or not to migrate some smartly selected set of templates.
But, as long as it is smart, maybe bugging the user is unnecessary because you can make all of them accessible, as discussed below.
There could be a problem where the server has many templates from many users, so including all of those in a dropdown for every user and every mission model could be problematic. Maybe a pattern for how other things are shared can be used (like for sharing scheduling goals). Forgetting how those are done, I could imagine that templates could be grouped by
So, when a user selects the template drop-down, they see those from group 1, and they can open up other groups somehow.
There are many ways this might be done. Feedback from this feature's requestors, Maggie Mende or Brad Clement, will be happily given.
The text was updated successfully, but these errors were encountered: