Nuno

[nunofaria11]

1. Implementing Description and Image for Todos

• Study the API response to understand the structure
• Add description and imageUrl fields to TodoDTO and TodoModel
• Update TodoRemoteDataSource, TodoRepository and TodoCubit to handle the new fields
• Modify the UI to display changes: Show the imageurl as a thumbnail and limit the description to max two lines

2. Implementing "Complete" Feature

• Modify the necessary layers, files, and classes to capture the isDone status from the API.
• Add the functionality to toggle a todo in the UI and also update the data in the backend to reflect those changes.

4. Bonus: Additional improvements (pick the ones you want)

• Improve the TodoFormScreen, so the user optionally can add description and imageUrl to their Todo when they create one
• Implement the "Favourite" feature, where you can locally save the favorited todos. Tip: You can use TodoLocalDataSource.
• Implement a todo detail page when the user taps on a todo to show the image bigger and with the full description.
• Implement a delete Todo functionality, where the user can delete todos on the list and also update the data in the backend to reflect those changes.

[sobimor]

Well done @nunofaria11 👏🏾
There are just a few minor comments, but overall, it was really good.

[sobimor]

suggestion (non-blocking): You could have request body DTO with a to json method to avoid creating/parsing JSON directly here

[sobimor]

issue: If the API call fails for any reason, we display an incorrect state to the user. In the catch block, you need to revert the state.

[sobimor]

issue: Please dispose of all controllers in the dispose method. (failing to dispose of it can lead to memory leaks)