Urql: next-urql: MultiPartFetchExchange not working

Created on 8 Jun 2020  路  3Comments  路  Source: FormidableLabs/urql

The multipartfetchexchange is not working in combination with next-urql.

It keeps sending application/json requests

Reproduction: https://codesandbox.io/s/github/BjoernRave/next-urql-multipart

Most helpful comment

Hey @BjoernRave

I fixed your sandbox for you, this can be confusing since we already updated our docs for the new major of next-urql.

For now exchanges are the second argument to withUrqlClient, you need to take the argument in account, working sandbox.

Example function:

const mergeExchanges = (ssrExchange) => [
        dedupExchange,
        cacheExchange,
        ssrExchange,
        multipartFetch,
      ]

All 3 comments

Hey @BjoernRave

I fixed your sandbox for you, this can be confusing since we already updated our docs for the new major of next-urql.

For now exchanges are the second argument to withUrqlClient, you need to take the argument in account, working sandbox.

Example function:

const mergeExchanges = (ssrExchange) => [
        dedupExchange,
        cacheExchange,
        ssrExchange,
        multipartFetch,
      ]

ahh, upps I messed it up then. Thanks for the clarification

Sorry about that! We鈥檝e kind of slipped in our release schedule and merged a PR that actually altered the docs and needed to wait 馃槄

Was this page helpful?
0 / 5 - 0 ratings

Related issues

fivethreeo picture fivethreeo  路  5Comments

danielres picture danielres  路  3Comments

alexraginskiy picture alexraginskiy  路  3Comments

kitten picture kitten  路  4Comments

ivosequeros picture ivosequeros  路  5Comments