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

RFC Inner types #163

Open
SerafimArts opened this issue Mar 14, 2018 · 0 comments
Open

RFC Inner types #163

SerafimArts opened this issue Mar 14, 2018 · 0 comments

Comments

@SerafimArts
Copy link
Member

SerafimArts commented Mar 14, 2018

As one of the encapsulation implementations, it makes sense to implement nested type support:

type Example {
    field: String
    field2: ID!
    field3: InnerType

    type InnerType {
        field: Example
    }
}

It is necessary to solve the problem of accessing external dependencies in case of name conflicts:

type Overrided {}

type Example {
    field: Overrided
    type Overrided { ... }
}

There is a conflict of names. Do I need to use an external or internal Overrided type? Obviously internal, but how in this case to appeal to the external?

Similar ideas: https://developers.google.com/protocol-buffers/docs/proto3#nested

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

No branches or pull requests

1 participant