Hide HTTP requests from the command log

[miklos-eiq]

Current behavior:

All XHR requests are printed to the command log, which can be distracting. There is no option to filter them. In #1184 it was mentioned this is possible by whitelisting requests with Cypress.Server.defaults, but that breaks stubbing.

Desired behavior:

Having an option, to only log stubbed XHR requests to the command log.

Maybe the best fix would be not a config option, but a toggle on the test runner, that can hide these logs.

Test code to reproduce

Test any app that does network requests.

Versions

Any OS and version.

[ckapilla]

I just found out this can be done easily programatically, see #1184

[ckapilla]

very interesting; thanks for flagging that issue

[agelico]

Updated to v8.2.0 and development turned into nightmare: all useless server pollings are back in the UI, couldn't find anything in intercept() to hide requests from UI and no plugin to bring server() functionality back. It looks pretty much like screenshots in #1184 all over again, and would gladly upvote changes requested here.

Did anyone find a way around it?

[OSIFOY]

This solution was working:

Cypress.Server.defaults({
    ignore: (xhr) => {
        return true;
    }
})

A couple versions ago, cant precise how many, but less than 2 months ago, it all appeared again.
I think we should get this fixed fast, it's impossible to navigate through all this logs and get those reports all messed up and useless cause its full of (xhr) and (fetch) logs..

What can we do or how can we help to get this issue fixed?

Version 8.4.0

[ebors-sysnetcz]

So we still dont have any answer or next version, when it will be fixed?

[the-bmc-dev]

This is really frustrating.

[simenbrekken]

I ran into this problem myself and after a deep-dive into Cypress' logging internals I discovered a novel workaround, simply hide fetch/XHR command log entries with CSS.

https://gist.github.com/simenbrekken/3d2248f9e50c1143bf9dbe02e67f5399

[samelawrence]

@simenbrekken This is working for me, thank you so much!

[MichaelBagnasco]

I think I found the line that broke the xhr ignore option. See line 187 of packages/driver/src/cy/commands/xhr.js. The changes in the commit were included in the 8.2.0 release when it started breaking for @agelico.

[Lasidar]

The workaround from @simenbrekken works great, but would love to see traction on the original issue, where XHR filtering seems completely broken.

[avorvul-grove]

Cypress can leave all XHR requests in the Command Log but make them folded in only one line to be unfolded on necessity: this may be the fastest and the cheapest way to solve the issue. How do you think, folks?