So That I can add new data to test how it would look with current implementation
Acceptance Criteria
Given a backend/API for adding new rhythms and rhythm codes
And we have a tree/list view of existing rhythms and rhythm codes
When I click "add rhythm"
Then ui (could be modal/could be in place) appears to allow entering data
And ui includes dropdown to select rhythm code (or there is one add rhythm button per rhythm code)
And ui includes necessary fields (title, description, video, etc.)
And ui has ability to input coordinates (ui edit of coordinates in follow-up story)
Given the "add rhythm" modal is visible
and valid data has been entered
When I click "save rhythm"
Then information is persisted to backend/API
And modal disappears
And rhythm appears in tree/list
Given the "add rhythm" modal is visible
When I click "cancel"
Then modal disappears
Given a backend/API for adding new rhythms and rhythm codes
And we have a tree/list view of existing rhythms and rhythm codes
When I click "add rhythm code"
Then ui (could be modal/could be in place) appears to allow entering data
And ui includes necessary fields (name)
And ui has ability to input coordinates (ui edit of coordinates in follow-up story)
Given the "add rhythm" modal is visible
and valid data has been entered
When I click "save rhythm"
Then information is persisted to backend/API
And modal disappears
And rhythm appears in tree/list
Given the "add rhythm" modal is visible
When I click "cancel"
Then modal disappears
Implementation Notes
the backend/API does not exist -> implement as part of this ticket
for now we can put coordinates for the rhythm codes + allow rhythms without coordinates (they could inherit coordinates from parent code, or go to 0,0, or not appear on the map)
garbage/non-valid data TBD (probably title is mandatory, coordinates (or default coordinates), description or video) -> followup ticket once you have decided what it should be
Story
As a website admin
I Want to be able to add rhythms and rhythm codes
So That I can add new data to test how it would look with current implementation
Acceptance Criteria
Implementation Notes
Checklist: