Breaking change in 0.1.17?
See original GitHub issueI was using graphql-tag 0.1.16 along apollo-client 0.5.0, then updated to 0.1.17 and 0.5.6 respectively, which introduced the following TypeError: Cannot read property 'kind' of undefined
raised from graphql-tag on GraphQL mutations.
This is what my mutation looks like:
apollo.mutate({
mutation: gql`
mutation {
newEntry(input: {
name: "${entry.name}",
description: "${entry.description}"
}) {
entryInfo {
name,
description
}
}
}
`
});
Though Iām really new to GraphQL so Iām afraid I canāt get what kind
could refer to š
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Changelog - Recipes
Breaking Changes. The tidy method for step_dummy now returns the original variable and the levels of the future dummy variables.
Read more >Release history - Event Data User Guide
Release History. This document describes substantial or breaking changes to the Event Data system. Changes. [2019-01-10] Change to Twitter URLs.
Read more >dev_compiler changelog
0.1.24. workaround breaking change on requestAnimationFrame ... 0.1.17. preliminary node module support; support for compiling / serving multiple html filesĀ ...
Read more >NEWS
... removes, doesn't deprecate) functions that were previously copied from other packages, introducing a few potentially breaking changes. ... Tmisc 0.1.17.
Read more >Changelog | Misk-Web
Many other potential breaking changes in refactor and release of SimpleNetworkDucks and SimpleFormDucks . API not stable and may be changed in upcomingĀ ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh, ughh, this is a bad bug. We should have a test for this. Even if we donāt encourage it, people defintitely do it.
Thanks for your help. I sort of felt that using interpolation wasnāt great because I had to wrap strings in quotes to get it to work. I will look into using GraphQL variables instead, thank you š