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

[new release] graphql_parser, graphql, graphql-lwt, graphql-cohttp and graphql-async (0.14.0) #21764

Merged
merged 14 commits into from
Jul 19, 2022

Conversation

andreas
Copy link
Contributor

@andreas andreas commented Jul 8, 2022

Library for parsing GraphQL queries

CHANGES:

…d graphql-async (0.14.0)

CHANGES:

- Support `__typename` on subscriptions (andreas/ocaml-graphql-server#178)
- Handle unknown fields for subscriptions (andreas/ocaml-graphql-server#178)
- Add ocamlformat (andreas/ocaml-graphql-server#177)
- Handle missing variables as null (andreas/ocaml-graphql-server#184)
- Show default value in introspection query (andreas/ocaml-graphql-server#194)
- Support block strings in the parser (andreas/ocaml-graphql-server#198)
- Handle skip/include directives on fragment spreads (andreas/ocaml-graphql-server#200)
- Improved handling of recursive arguments and objects (andreas/ocaml-graphql-server#199)
- Fix websocket conflict (andreas/ocaml-graphql-server#206)
- Update deprecated Fmt functions (andreas/ocaml-graphql-server#206)
- Use Yojson `t` types instead of deprecated `json` type (andreas/ocaml-graphql-server#208)
- Raise minimum `rresult` version (andreas/ocaml-graphql-server#209)
@andreas
Copy link
Contributor Author

andreas commented Jul 19, 2022

Many of the build failures seem to be due to a irmin dependency bug. I've tried summarising the issue here: mirage/irmin#1843 (comment)

I'll wait for that conversation to be resolved before continuing with this PR.

@kit-ty-kate
Copy link
Member

Many of the build failures seem to be due to a irmin dependency bug. I've tried summarising the issue here: mirage/irmin#1843 (comment)

I'll wait for that conversation to be resolved before continuing with this PR.

I fixed the issue in #21839, sorry i forgot about this PR. It should be good to go once CI passes.

@kit-ty-kate
Copy link
Member

Thanks! Sorry for the wait

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

Successfully merging this pull request may close these issues.

2 participants