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

Disconnect map name from missionRun object #1864

Open
andchiind opened this issue Dec 10, 2024 · 0 comments
Open

Disconnect map name from missionRun object #1864

andchiind opened this issue Dec 10, 2024 · 0 comments
Labels
backend Backend related functionality improvement Improvement to existing functionality

Comments

@andchiind
Copy link
Contributor

Describe the improvement you would like to see
It should be possible to update the map for a missionrun without having to change all past missionruns as well. One way is to link a missiondefinition to a MapMetadata instead of a missionRun. Another is to make MapMetadata not an owned property but instead its own table. Both of these options will make it much easier to rename maps or to change their boundaries of transformation matrices.

How will this change existing functionality?
It will make it much easier to update maps as they will not be tightly coupled to previous missionruns.

How will this improvement affect the current Threat Model?
N/A

@andchiind andchiind added backend Backend related functionality improvement Improvement to existing functionality labels Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Backend related functionality improvement Improvement to existing functionality
Projects
None yet
Development

No branches or pull requests

1 participant