Arda TANRIKULU
Arda TANRIKULU
### 🚀 Snapshot Release (`alpha`) The latest changes of this PR are available as `alpha` on npm (based on the declared `changesets`): | Package | Version | Info | |------|---------|----|...
### 💻 Website Preview The latest changes are available as preview in: [https://8f0f7cb0.fets.pages.dev](https://8f0f7cb0.fets.pages.dev)
Sounds interesting! About `parse` function, `onParse` hook can be used to replace the `parse` function; ``` { onParse({ setParseFn }) { setParseFn(customParse); } } ```
For sure, we can use that parse fn in everywhere so codegen, mesh and hive can benefit from.
Hmm interesting use case, but if we do that, this won't be valid anymore for status codes; https://the-guild.dev/graphql/yoga-server/docs/features/error-masking#modifying-http-status-codes-and-headers Some users want to return different status codes for auth if the...
Due to the current design of Yoga, it is not possible with the Fetch based API we currently provide but depending on what you use as a server underneath you...
That's a great idea! https://github.com/dotansimha/graphql-yoga/pull/3236 I think we can use `onValidate` instead of string matching because comments and some other cases I added in the tests can bypass the current...
https://github.com/dotansimha/graphql-yoga/pull/3219/files I created an example for you. But later, I guess we should document it.
I agree with @kamilkisiela . It should be behind a flag at least because it conflicts with graphql-http compliance tests.
It'd be great @EmrysMyrddin There are still issues with TS stuff.