Comments (6)
@enisdenjo noticed that I was using a callback with express-graphql
and it had been working. However, that way it doesn't work with graphql-http
since it's not a valid argument as it seems to expect an object.
graphqlHTTP((req) => ({
schema
}));
graphqlHTTP({
schema
});
At least now I know what's the problem and it's on my end.
from graphql-http.
@chongma, not sure, I just ended up migrating to Yoga GrahpQL which wasn't too bad: https://the-guild.dev/graphql/yoga-server/docs/migration/migration-from-express-graphql
from graphql-http.
i guess it is using the formatError
function now https://github.com/graphql/graphql-http/blob/main/docs/modules/handler.md#formaterror
from graphql-http.
Hey thanks for reporting. Can you please share your server implementation code? Are you sure you're providing a schema?
from graphql-http.
I am also migrating from express-graphql
but I have been using the callback. How do I keep it?
from graphql-http.
It seems to work like this
router.use(path,
middleware,
(req, res) => {
// ... do something
const handler = createHandler({
schema,
context: {
loaders: createLoaders(),
user,
ipaddress: req.ip
},
customFormatErrorFn: function (err) {
// this should catch any unhandled errors from the resolvers
console.error(err)
}
})
handler(req, res)
})
The trouble I am having now is whether customFormatErrorFn
will work as expected
from graphql-http.
Related Issues (20)
- Export parseRequestParams similar to express-graphql HOT 5
- Add extensions function to createHandler
- UTF-8 body corruption HOT 2
- When checking the Accept header the charset is expected to be utf8 not utf-8 HOT 2
- Compatibility with graphql-upload
- Response containing errors parsing variables is nested twice HOT 3
- externalize audits so they can be run locally and/or within target library CI/CD HOT 3
- Missing variable coercion failure audit HOT 2
- Allow Deno to clean up leaked test resources HOT 1
- Add to the context values the response of the route, because it is usefull for set cookies for example. HOT 8
- `Module '"graphql-http"' has no exported member '...'` happens with ESM TypeScript HOT 4
- Forks should be able to change the audits.yml file
- Add graphiql in createHandler method HOT 2
- Responses from createHandler in express are not returned HOT 2
- graphql-http vulnerable to CSRF attack
- Support for graphiql HOT 2
- Unable to migrate from express-graphql: loads forever
- Graphiql:true not working - {"errors":[{"message":"Missing query"}]}
- `graphql` seems to have an issue with vite-node HOT 1
- Add Graphiql HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from graphql-http.