Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[question] Domain objects based on GraphQL types #12

Open
RafaO opened this issue Mar 7, 2022 · 0 comments
Open

[question] Domain objects based on GraphQL types #12

RafaO opened this issue Mar 7, 2022 · 0 comments

Comments

@RafaO
Copy link

RafaO commented Mar 7, 2022

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant