Skip to content

[question] Domain objects based on GraphQL types #12

Open
@RafaO

Description

@RafaO

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!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions