Skip to content

update documentation on graphql-kotlin #965

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

Merged
merged 1 commit into from
Nov 19, 2020

Conversation

dariuszkuc
Copy link
Contributor

Add documentation on graphql-kotlin (https://github.com/ExpediaGroup/graphql-kotlin) usage for creating reactive GraphQL server and http client.

Add documentation on `graphql-kotlin` (https://github.com/ExpediaGroup/graphql-kotlin) usage for creating reactive GraphQL server and http client.
@dariuszkuc
Copy link
Contributor Author

FYI attempting to start gatsby from latest source didn't work for me due to the conflicting graphql versions

> npm list graphql
@0.0.0 /path/to/project/graphql.org
├─┬ [email protected]
│ ├─┬ [email protected]
│ │ └─┬ [email protected]
│ │   └── UNMET PEER DEPENDENCY [email protected] 
│ ├─┬ [email protected]
│ │ └── [email protected] 
│ └── UNMET PEER DEPENDENCY [email protected] 
└── [email protected] 

npm ERR! peer dep missing: graphql@^14.4.1, required by [email protected]
npm ERR! peer dep missing: graphql@^14.4.1, required by [email protected]
npm ERR! peer dep missing: graphql@^0.10.5 || ^0.11.3 || ^0.12.0 || ^0.13.0 || ^14.0.0, required by [email protected]

Downgrading graphql package to 14.7.0 worked locally.

@orta
Copy link
Member

orta commented Nov 19, 2020

Yeah, we need to remove the npm instructions - good reminder.

Nice idea, having two different descriptions for the lib in client and server

@orta orta merged commit 2e4c1eb into graphql:source Nov 19, 2020
@dariuszkuc dariuszkuc deleted the graphql_kotlin branch August 3, 2021 15:08
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