External Database

[CharlineOe]

Value proposition

As a user of the DIY App I want to have access to it via different devices In order to use it flexible in different phases (for detailed information and browsing ideas on the laptop, but on my smartphone during the construction phase).

Description

Acceptance criteria

• the data is accessible on different devices
• changes (e.g. adding a project) are stored in the external database
• Custom error messages are provided to enhance user understanding of the issue.
• Clear indicators are displayed for data loading states across the app, ensuring users are informed during data retrieval or processing phases.

Tasks

• [ ] create new branch feature/backend
• [ ] create a MongoDB-account for the DIY-team and set up the initial projects-database
• [ ] connect the code with MongoDB = fetch, add the .env.local-file to gitignore
• [ ] add error handling (404 etc.)
• [ ] create required Mongoose schemas
• [ ] create API routes to handle CRUD operations
• [ ] refactor existing code to use API database endpoints

[JessicaLoers]

Nice one. ✨ I have a few comments regarding the acceptance criteria - as always 🤓

💡 We always describe the acceptance criteria from the user's point of view. For this reason, the following points could be deleted.

• [ ] use Mongoose to handle database transactions
• [ ] Mongoose schemas are in place

However, you could add the following points to the criteria:

• [ ] Custom error messages are provided to enhance user understanding of the issue.
• [ ] Clear indicators are displayed for data loading states across the app, ensuring users are informed during data retrieval or processing phases.

As an additional future feature, you could consider implementing a loading spinner or a skeleton. 🛸