Update Service Cards

[Alexander-Iantbelidze]

Value proposition

As a User I want to edit service cards In order to i can update service cards if the card needs changes

Description

The User will be able to locally edit the service card allowing the input fields to appear directly on the card. After saving the changes the card will be displayed again.

Acceptance criteria

Edit:

   -[ ] User can select an existing Service Card and edit, save and display the information
   -[ ]  Changes persist in Frontend

Tasks

• [ ] Create Branch edit-service-card
• [ ] Create useState for edited Cards
• [ ] Write a handleEditServiceCard, handleEdit and handleSave function
• [ ] Use conditional rendering for edit and no edit modus
• [ ] The User can click on an edit button and start making changes on the service card
• [ ] After change the User is able to click on the save button

[ThomasKirst]

The story looks good so far. However, I would add the wireframe of the edit form with the pre-filled data from the ServiceCard. You should be able to reuse one of your former layouts for this and slightly adjust it – with an "Update" button instead of "Create" or something similar. Then it would also be clear where the form appears. Not that there are misunderstandings and one wonders, is the Service Card now edited directly on the spot or does the user come to an extra page where the form is edited.

Something minor: we usually name branches like update-service-cards instead of camelCase.

Great you´re mentioning input validation which is an important task here 👍

[ThomasKirst]

All good! I would name the branch something like feature/edit-service-card or similar, though. It would be great to get a visual idea of how the card would look like in the edit mode, but it´s not a must.