Integrate Database and save button

[ketnek]

Value proposition

As a user I want to save my created routes in order to keep and don't forget them.

Description

Acceptance criteria

• [ ] Clicking the save icon opens a form
• [ ] After the user add a name and some notes, clicking the save button will save the route
• [ ] Clicking the Cancel button brings him back to the draw mode and he can make some changes on his route before save it

Tasks

• [ ] create a mongoDB database named bicycle
• [ ] create a collection named routes into it
• [ ] render a save button by using the ControlButton component
• [ ] create a Form component for user input with two buttons
• [ ] implement POST request to save new routes data in the routes collection
• [ ] set a onSubmit handler on the form to trigger the POST request

[mbosselmann]

Hi Kevin, I like your user story! :octocat: But I have two questions:

1. As you wrote in your acceptance criteria, this is a story to implement the backend. I think the value of this user story would be that the drawn routes would be available for different devices (instead of saved routes in your local storage in comparison). Therefore, I would adapt the value proposition to make this more clear.
2. Is this a user story for one CRUD operation (READ)? I think so, but maybe you can make this more visible in your tasks. my suggestion: Instead of "connect it to frontend" maybe "implement GET request to display routes data in the frontend" is a better task description. :)

I hope this does help! Feel free to ask if you have questions. :)

[ketnek]

Hey Mareike, thanks for your feedback and your suggestions.😃 First point: I'm totally agree and I will change the acceptance criteria. Second point: I guess I will need three CRUD operations, because I would like to give the user the opportunity to save, read and delete. But you are right it would be much nicer to point that out in my task description👍🏻

[mbosselmann]

Hi Kevin, great job! 👍 I like that you thought about my questions, but I would recommend to have one user story for every CRUD operation to have less complexity. Yesterday I thought that this is the user story for one CRUD operation so maybe this was a misunderstanding? 🤔

[ketnek]

Hi Mareike, to be honest I don't thought about any CRUD operations yesterday.😅 But I wrote I want to connect my front and backend and I guess that was my mistake and our misunderstanding. At this point I like to only set up a database and later I will use the CRUD operations to connect it with the frontend. So I would suggest I delete the CRUD implementations from my story and later I will write separate ones for them. What do you think?

[CJAkkuec]

Little typo here,

Clicking the save icon will save the drown route

I hope it's not a drown route, but a drawn one. 🙈

[ketnek]

I guess that would be pretty unique and definitely somethings special. But you are right. It is not a drown route😂 Thanks for that😊