🔧 Day 34. Response
Nachrichtenbereich: 🔧 Programmierung
🔗 Quelle: dev.to
What I did:
I worked on the problem of deserializing a response that can have different models in it? Generally, It's not the a problem with Ktor; the serialization library is responsible for that. In our case, we use kotlinx.serialization library for that. I found the solution in the official documentation.
Now, I know how to solve the problem with multiple variants of response. I think I need an hour to finally implement that case. But I have two unsolved problems. The first is error handling. The second is handling basic responses.
What I will do:
- Update README file with description of project.
- Fix comment element
- Implementation of WebView to display stub content
- Theme configuration for Lottie animation
- Create public collection of API calls in Postman
If you want to join the project, just leave a comment here, or write a message in LinkedIn.
What help I'm looking for:
Designer (create design of application in Figma)
Android/KMM developer
Any other help related to the project.
My timeline:
Day 1. Deep breath and dive.
Day 2. Networking layer.
Day 3. Loading of articles.
Day 4. ArticleItem.
Day 5. Localization.
Day 6. Work on Sunday.
Day 7. First week.
Day 8. Enjoying coding.
Day 9. Expect/actual.
Day 10. TODOs.
Day 11. Friday evening.
Day 12. Frustration.
Day 13. Blocker
Day 14. Monday
Day 15. Reactions
Day 16. Feed
Day 17. stringWithFormat
Day 18. Comment
Day 19. 1 percent
Day 20. A bit of progress
Day 21. Pagination
Day 22. Lottie animation
Day 23. Sorting of articles
Day 24. Step by step
Day 25. Broken endpoint?
Day 26. After party
Day 27. Burnout
Day 28. Opportunity for growth
Day 29. Hard work
Day 30. Old code
Day 31. Technical debt
Day 32. API calls
Day 33. Generic response
See you tomorrow.
...
🔧 Day 34. Response
📈 11.9 Punkte
🔧 Programmierung
🔧 Day 33. Generic response
📈 11.9 Punkte
🔧 Programmierung