You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi! First of all, thank you for this repo. I am exploring KMM + GraphQL and this was really helpful and inspirational.
Now the question: Do you think that having repositories and UI layer relying on GraphQL types instead of regular Kotlin data classes could have limitations at some point? There is always the possibility of writing Kotlin extensions if you need anything extra, but for annotations like @serializable, it could be an overhead.
What's your opinion? If that is the case, I'm happy to work on a PR to showcase the domain classes and how I think the mapping can work between them.
Thank you!
The text was updated successfully, but these errors were encountered:
Hi! First of all, thank you for this repo. I am exploring KMM + GraphQL and this was really helpful and inspirational.
Now the question: Do you think that having repositories and UI layer relying on GraphQL types instead of regular Kotlin data classes could have limitations at some point? There is always the possibility of writing Kotlin extensions if you need anything extra, but for annotations like @serializable, it could be an overhead.
What's your opinion? If that is the case, I'm happy to work on a PR to showcase the domain classes and how I think the mapping can work between them.
Thank you!
The text was updated successfully, but these errors were encountered: