Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Do not truncate cy.log() in Command Log #5625

pitgrap opened this issue Nov 7, 2019 · 2 comments · May be fixed by #5630


Copy link

@pitgrap pitgrap commented Nov 7, 2019

This is a feature request.

Current behavior:

Long messages in cy.log() gets truncated to a single line. On screenshots the panel of cyress is always very narrow, so the log is almost never readable.


Desired behavior:

It would be great to not truncate or at least support a flag to disable the truncation in cy.log(). Especially URLs and other import informations should be displayed.


Steps to reproduce: (app code and test code)

  it("example", () => {
    cy.log("Lorem ipsum dolor sit amet, consetetur sadipscing elitr, sed diam nonumy eirmod tempor invidunt ut labore et dolore magna aliquyam erat, sed diam voluptua. At vero eos et accusam et");


3.4.1 to 3.6.0


The following CSS rule is responsible for all message-types (cypress_runner.css:4016):

.reporter .command-message {
  white-space: nowrap;

Maybe add a style just for the log (or all entries like URLs in cy.request()?):

.reporter .command-name-log .command-message {
  white-space: initial;
  word-break: break-word;

This comment has been minimized.

Copy link

@jennifer-shehane jennifer-shehane commented Nov 7, 2019

This is something we agree should be changed.

CSS that requires changing:

We would love an open PR. Check out our contributing doc .

@jennifer-shehane jennifer-shehane changed the title Do not truncate cy.log() Do not truncate cy.log() in Command Log Nov 7, 2019
@pitgrap pitgrap referenced a pull request that will close this issue Nov 7, 2019

This comment has been minimized.

Copy link

@pitgrap pitgrap commented Nov 7, 2019

Hi @jennifer-shehane, I opened a PR for this small feature: #5630

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
You can’t perform that action at this time.