Should-have: Your prototype API has 3 to 5 working request (Viewing and changing requests)
Should-have: Your prototype API has 3 to 5 working request (Viewing and changing requests)
We have more than this, see swagger
Should-have: Your API is designed (not implemented yet to cover 10 use cases)
Should-have: Your API is designed (not implemented yet to cover 10 use cases)
API designed in last learning field. Actix-web for HTTP request. Matches it to incoming functions -> execute DB statements with a db function -> return value
Must-have: Your prototype API has one working request
Must-have: You have implemented at least one test on unit level
Must-have: You have implemented at least one test on unit level
Already done 5 Unit tests implemented for validating Redis/Postgres connection string more to follow
Should-have: You have a visual representation of the API
Should-have: You have a visual representation of the API
Same as other ticket. Show via Swagger or Bruno how API is consumed and what the output is
Could-have: Your prototype API has 6 working request (Viewing and changing requests)
Could-have: Your prototype API has 6 working request (Viewing and changing requests)
Already done in API
Could-have: You show on prototype level how your API is consumed via a backend service or a GUI
Could-have: You show on prototype level how your API is consumed via a backend service or a GUI
Swagger-Bruno to visualize what the API takes as an Input and what the Output is Otherwise Frontend would be an option
Could-have: You have defined and described and maybe implemented a way to test your API on integration or E2E level.