DB - Read

[Alexander-Iantbelidze]

Value proposition

As a User I want to view my Service Provider Cards on various devices. In order to have a persistent access to my Service Offers.

Description

By connecting to a database, Users can retrieve and read Service Cards from all devices and browsers. In addition, during fetching, a "loading..." text is displayed. If fetching the Service Cards did not work, an error message is displayed.

Acceptance criteria

• [ ] The created Service Provider Cards are stored persistently for the User and accessible from any device.
• [ ] While the User is waiting for the Service Provider Cards to be displayed, he will be informed by the text "loading...".
• [ ] If the Service Provider Cards cannot be loaded, an error message should be displayed.

Tasks

• [ ] Create branch db-read-service-cards
• [ ] Create a database to which all team members have access
• [ ] Create the connection to the database
• [ ] Create a database schema that aligns with the nested structure of the array of objects
• [ ] Create a read function (GET-method!)
• [ ] Use SWR to fetch the data from the database
• [ ] Ensure a message for the isLoading process during the fetch
• [ ] Ensure an error message if the fetch failed

[mbosselmann]

Hi Team ServiceCircle, another good start! 💪 Here are my remarks:

Value Proposition:

• I think the value of implementing the read functionality is not to save service cards. It is only the possibility to read service cards from any device. My suggestion:

As a user, I want to view my services on various devices, to ensure easy, persistent and convenient access to my service offers.

Description: Even though the service list wont' change, some things differ from before and should be shown with wireframes:

1. There will be a loading state of the data. As the fetching of the data will need some time you should add what will happen while fetching. :)
2. There should also be a error text displayed that explains to the user what happened when it was not possible to load the data. See for example the first example user story of the movie app in our capstone docs.

Acceptance criteria/Tasks

• These should be updated too according to the suggested changed to the description. :)

I hope this does help. :)

[Alexander-Iantbelidze]

Hi Team ServiceCircle, another good start! 💪 Here are my remarks:

Value Proposition:

* I think the value of implementing the read functionality is not to save service cards. It is only the possibility to read service cards from any device.  My suggestion:

As a user, I want to view my services on various devices, to ensure easy, persistent and convenient access to my service offers.

Description: Even though the service list wont' change, some things differ from before and should be shown with wireframes:

1. There will be a loading state of the data. As the fetching of the data will need some time you should add what will happen while fetching. :)

2. There should also be a error text displayed that explains to the user what happened when it was not possible to load the data. [See for example the first example user story of the movie app in our capstone docs.](https://web-capstone-docs.neuefische.de/guides/user-stories#1-movies-list)

Acceptance criteria/Tasks

* These should be updated too according to the suggested changed to the description. :)

I hope this does help. :)

thank you! 👍🏻 . Edited. :)