fix(debug): use debug verbosity in debugExchange
Summary
The debug exchange currently outputs at a verbosity of log. However I think it makes more sense to use debug because that is the name of this package and the console gets littered with log messages without some other approach to minimize that output.
This change should hopefully promote more usage of this exchange as it can easily be toggled from the console.
Set of changes
- Changes the console output verbosity from
logtodebugin thedebugExchange
🦋 Changeset detected
Latest commit: a83fbb578b55e0a3de930aff4f2e8dfd77eec2e7
The changes in this PR will be included in the next version bump.
This PR includes changesets to release 1 package
| Name | Type |
|---|---|
| @urql/core | Patch |
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
I tried to follow the instructions from the bot for changeset but it isn't working. Neither npx changeset or yarn changeset are working for me. Could someone please add the changeset for me or show me how to get that automated process working?
Friendly ping on this. It would really help my workflow to separate debug messages from log messages.
Seems the commit here has caused a split in what's reconcilable and the added push has broken mergeability here: https://github.com/onx2/urql/commit/d578b5b297a7f59ee98e7a53c0bcccb401cbb896
I'm a bit late on this, I realise, the problem here however is that the PR has been opened from a main branch, and the merge commit makes it hard to add commits for maintainers as per what GitHub enables me to send to the branch.
I'll close this out and will issue a replacement PR, since that's the easiest option at this point