search

Nesssaaa / capstone-flashcard-app

https://capstone-flashcard-app-zeta.vercel.app
4 stars 3 forks source link

User Story - Delete Cards #8

Open Nesssaaa opened 7 months ago

Nesssaaa commented 7 months ago

Value proposition

As a user I want to delete cards that I don't need anymore, so that I only see relevant content for my learning journey.

Description

Image

Acceptance criteria

Tasks

MerleMak commented 7 months ago

Nice! If you want to have a prettier modal (The window that pops open to ask if you really want to delete de card) you can also implement a library that handles these modals for you. This could also be an extra userstory :) For the basic functionality i think this is enought for now!

MerleMak commented 7 months ago

Suggestion:

As a user I want to delete cards that I don't need anymore So that I only see relevant content for my learning journey

Please edit the wireframe so it doesn't include the "Soll diese Karte wirklich gelöscht werden?" because its not part of this US yet :)

Nice job!

Nicole-Schwarz commented 7 months ago

@MerleMak Your comment concerning the confirm message is not clear to us. Shall we delete the confirm message completely? The functionality is important in our opinion. Shall we do it with window.confirm oder directly with the React Suite library? THANKS :)

MerleMak commented 7 months ago

Oh okay, I didn't realise that the confirmation is supposed to be part of this user story!

You have several options for this. The mood-diary team is taking this approach: https://github.com/users/MathiSans/projects/1/views/1?pane=issue&itemId=54595398 Of clicking the delete button, then the button changes the text to "really?" and then you have to click again to confirm!

Another option is to work with a library to implement a confirm pop-up window (this is called a modal) I wouldn't use React Suite library though, its quite a big library for only implementing a modal.

The option window confirm i think is not so flexible, because the default confirmation pop up generated by the browser look a bit old school :D

I think it is best to implement the delete feature without the confirmation for now. This user story has a good size like it is now.

I would suggest you write a new user story where you implement option one or two for the delete confirmation, depending which approach you like.

so this user story: Just add the delete functionality without confirmation add a new user story: Implementing a confirmation for the delete function

Small user stories are always better :)