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

input forceNoColor does not work. #50

Open
viperx77 opened this issue Jan 30, 2019 · 3 comments · May be fixed by #86
Open

input forceNoColor does not work. #50

viperx77 opened this issue Jan 30, 2019 · 3 comments · May be fixed by #86

Comments

@viperx77
Copy link

Newman option is documented as:

--color
Enable or Disable colored CLI output. The color value can be any of the three: on, off or auto(default).
With auto, Newman attempts to automatically turn color on or off based on the color support in the terminal. This behaviour can be modified by using the on or off value accordingly.

But code uses:

    let forceNoColor = tl.getBoolInput('forceNoColor');
    newman.argIf(forceNoColor, ['--no-color']);
@carlowahlstedt
Copy link
Owner

Link to docs.

It seems --no-color has been removed.

@sebcaps
Copy link
Contributor

sebcaps commented Feb 20, 2019

In addition changes were made for HTML report, I guess not a common used option, but we should envision a support for postman version 4 ?

@carlowahlstedt
Copy link
Owner

I would say we update the task to support the latest version. When you're installing it on a hosted agent, whatever is installed by npm by default is what people will be using. I would assume postman isn't planning to support older versions, but something we should probably look into

@satano satano linked a pull request Aug 31, 2020 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants