question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

feature request to turn off text wrapping or force a width larger than 60 for console.log events

See original GitHub issue

The CLI reporter should have to ability to configure the text wrap limit for console.log events. In a build environment such as TeamCity we are restricted to just 60 chars. The requests api’s and their stats are not wrapped at all. This behaviour was not present in release 2

The user should be able to…

  • to turn off wrap for console.log events
  • and/or, increase the default width from 60

Version and environment information:

  1. Newman Version (can be found via newman -v): 3.5.2
  2. OS details (type, version, and architecture): All Supported
  3. Are you using Newman as a library, or via the CLI? Library
  4. Did you encounter this recently, or has this bug always been there: encountered in release 3. Not present in release 2
  5. Expected behaviour: ability to turn off wrap or increase text width that is defaulted to 60 for console.log events
  6. Command / script used to run Newman: N/A
  7. Sample collection, and auxilliary files (minus the sensitive details):
  8. Screenshots (if applicable):

Steps to reproduce the problem:

  1. engineer a collection, where in the test script, there is console.log instruction that prints out a string longer than 60 chars
  2. run newman library in an environment where the shell is not a tty. (i.e. in a build environment such as TeamCity)
  3. the wrap will default to 60

Note: I’ve tried setting TERM=xterm in the environment or CI=false

Issue Analytics

  • State:open
  • Created 6 years ago
  • Reactions:4
  • Comments:8 (1 by maintainers)

github_iconTop GitHub Comments

2reactions
ChieftainY2kcommented, Jul 2, 2021

Hello, any news on that ? The line wrap limit at 60 is reeaaaaal PITA , if you will 😃

2reactions
sstidlcommented, Jun 25, 2021

Hi! Two Years of silence here. I find it still hard to read, when output is wrapped at col 60.

Can anyone take this task or tell me how I could contribute?

regards, S

Read more comments on GitHub >

github_iconTop Results From Across the Web

Specify the text-wrapping options for a control
Right-click the control for which you want to enable or disable text wrapping, and then click Control Properties on the shortcut menu. Click...
Read more >
Wrapping and breaking text - CSS: Cascading Style Sheets
This guide explains the various ways in which overflowing text can be managed in CSS.
Read more >
Keyboard Control - mpv.io
Depending on platform, a variety of different video and audio output methods ... without being wider than 70% of the screen width, or...
Read more >
Config Cheat Sheet - Docs
DISABLE_MIGRATIONS : false: Disable migrating feature. ... -1 to turn off. MAX_TIMEOUT : 60s. ... Shutdown will be forced if it takes longer...
Read more >
Configure Grafana | Grafana documentation
You can customize your Grafana instance by modifying the custom configuration file or by using environment variables. To see the list of settings...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found