Skip to content

Not duplicate things with resolver and schema #15

@Dracks

Description

@Dracks

Is your feature request related to a problem? Please describe.
I don't like to repeat work, and create a variable of schemas and a variable of resolves, can always be a focus of problems.

Describe the solution you'd like
Someway, maybe using macros, create a uniq schema with the resolvers, to generate the schema definition, and be sure that the same field has the correct resolver

Describe alternatives you've considered
Something like type-graphql, will be a good idea:

@query(type="String)
function hello
 return "World
end

schema = Dict("hello"=>hello)
graphql.schema(schema)

Additional context
Add any other context or screenshots about the feature request here.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions