Skip to content
This repository has been archived by the owner on Jul 18, 2023. It is now read-only.

Roadmap #27

Open
byme8 opened this issue Jun 27, 2022 · 3 comments
Open

Roadmap #27

byme8 opened this issue Jun 27, 2022 · 3 comments

Comments

@byme8
Copy link

byme8 commented Jun 27, 2022

At first, I thought that it was an excellent library. It just needs some polish to be good enough. Then I played around with it and saw that it is just a proof-of-concept with neet idea where lots of essential features are just not implemented. It looks like adding them will be somewhat tricky.

So, is there any roadmap for the library?

@Giorgi
Copy link
Owner

Giorgi commented Jun 27, 2022

Apart from the PRs that you submitted, what are other missing essential features?

I'll review your PRs in details in a day or two and accept them.

@byme8
Copy link
Author

byme8 commented Jun 27, 2022

From what I see, the library is missing the following key features. Without them, graphql is not graphql.
Mutations
It is a crucial feature, but it is easy to implement. So, no worry about it.

Type nullability
It may take a noticeable amount of effort to implement.

Update: ok, type nullability is not so complex

Ability to combine multiple fields in one query
At the moment, it is not possible to build and execute a query when you are touching various fields at the same time:

{
  users{
    name,
    rocket
  },
  company{
    ceo,
    founded
  },
  missions {
    id,
    description
  }
}

I don't see an easy way to add support for it. It will definitely require a lot of consideration.

@Giorgi
Copy link
Owner

Giorgi commented Jul 9, 2022

I think type nullability has a higher priority because it is needed to implement mutations correctly.

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

No branches or pull requests

2 participants