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
{{ message }}
This repository has been archived by the owner on Jul 17, 2023. It is now read-only.
erotondo opened this issue
May 5, 2021
· 2 comments
Labels
BacklogA backlogged issue that still needs to be completedEditorAn issue related to the editor component of the softwareFrontendAn issue handled by the frontend developersGit-KingsFrontend
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.
The text was updated successfully, but these errors were encountered:
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
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.
This is a required feature. Note, it cannot really be addressed until all other aspects of version control have been completed.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
BacklogA backlogged issue that still needs to be completedEditorAn issue related to the editor component of the softwareFrontendAn issue handled by the frontend developersGit-KingsFrontend
Frontend (editor) version control
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.
The text was updated successfully, but these errors were encountered: