Tobias Tengler

@captbaritone I fixed the conflicts :)

The proposed solution using the `package.json` export would not alter the signature of useFragment or useRelayEnvironment. Just a different implementation would be used whether the code is executed in Server...

Super excited about this change - especially the deprecation part. @eMerzh would you mind also adding the `@deprecated` JSDoc for deprecated arguments, input fields and enum values? Especially input fields...

> Libraries like React Query can essentially work the same as they do today. They can either use `use` internally, or they can return a promise to the caller, and...

I believe the schemaExtensions is supposed to point to a directory that contains *.graphql files with the extensions. At least that is what has worked for me...

This actually happens if there are **any** errors in executable documents when starting the LSP. We got multiple reports from product engineers that autocompletion is no longer working, because they...

I don't think errors fit Relay's data consistency tenet. I want actual data to be synchronized across surfaces, but I find it very hard to find use cases where one...

How do you differentiate between a expected and unexpected error? We model expected errors in our schema. Though only on the mutation-side atm, because we haven't yet had a case...

Yes. If a field is associated with an error, the new value (`null`) should not replace a previously successfully retrieved value in another query. Hooks attempting to read out a...

I think you can do typeaheads just fine with the existing API. ```js function Typeahead() { const [search, setSearch] = useState("") const deferredSearch = useDeferredValue(search) return setSearch(e.target.value)} /> } function...