Day 33. Generic response

I think being only an Android developer is too narrow today. You need to have broader knowledge and skills to solve tasks outside single-platform development. AI tools push us in this direction, but at the same time, they help us gain this expertise.

What I did:

Today, I worked on a search endpoint. I planned to complete it, but I only implemented the search logic for articles. I found that the article, user, and organization models were different from those I had used before. I decided to extract a separate model for it and simply add a mapper to the domain article model. Additionally, I set all fields to nullable to avoid the situation where a value doesn't pass through. It's a good strategy to protect yourself, especially when you're unsure of the response model.

Another problem is that I can't specify a generic type for the response model in Ktor. I received error indicating that generic aren't allowed. I think there should be a solution for this problem because it's a very common scenario. It's a good topic for investigation, and it would be interesting to find a solution for how to serialize objects based on the response.

What I will do: