Skip to content
This repository has been archived by the owner on Jul 17, 2023. It is now read-only.

Editor Version Control #279

Open
erotondo opened this issue May 5, 2021 · 2 comments
Open

Editor Version Control #279

erotondo opened this issue May 5, 2021 · 2 comments
Labels
Backlog A backlogged issue that still needs to be completed Editor An issue related to the editor component of the software Frontend An issue handled by the frontend developers Git-Kings Frontend

Comments

@erotondo
Copy link
Collaborator

erotondo commented May 5, 2021

Frontend (editor) version control

  • Likely should be implemented/located on the logistics page of a scenario or a popout window should appear when you click on the edit button of a given scenario.
  • Will involve whoever is working on the backend and database

BACKLOGGED: Ran out of time to implement; needed to focus on integrating with the backend team to set up new endpoints that worked with the new schema before deploying changes to the server.

@erotondo erotondo added Git-Kings Frontend Backlog A backlogged issue that still needs to be completed Frontend An issue handled by the frontend developers Editor An issue related to the editor component of the software labels May 5, 2021
@erotondo
Copy link
Collaborator Author

erotondo commented May 5, 2021

To clarify, all that really needs to be done is adding a GUI component (dropdown menu?) that appears for each scenario and can be used to specify what version should be used/is being accessed.

@erotondo
Copy link
Collaborator Author

erotondo commented May 5, 2021

This is a required feature. Note, it cannot really be addressed until all other aspects of version control have been completed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Backlog A backlogged issue that still needs to be completed Editor An issue related to the editor component of the software Frontend An issue handled by the frontend developers Git-Kings Frontend
Projects
None yet
Development

No branches or pull requests

1 participant