Option to force on in production

[adamscybot]

At the moment, the exchange is a no-op when NODE_ENV is production. There are use cases where you want to keep this enabled in prod -- to analyse the requests/responses.

We could change the API of the exchange to be a higher order function that accepts a new config option enabled?: boolean which defaults to NODE_ENV !== 'production'.

This will allow people to control when the exchange is and isn't in affect.

Willing to PR if you think this is a good idea.

[andyrichardson]

@adamscybot this is a fair point.

Your suggestion of a HOF sounds like a strong idea. Get a PR open and we'll get this merged 👍

[adamscybot]

Actually, thinking about this again, would it better to just remove the checks entirely and defer this to userland? E.g. the user simply puts a conditional in their exchanges array .

I think this removes any elements of surprise and it doesn't set a precedence. It also means we don't have a no-op pipe there when its off.

[JoviDeCroock]

We're open for a PR to do this in @urql/devtools. The thing is that in Production you'll be lacking display names for your components since you are minified anyway.