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

Powershell error table formatting issue #3603

Closed
TommyE123 opened this issue Jun 2, 2024 · 1 comment · Fixed by #3620
Closed

Powershell error table formatting issue #3603

TommyE123 opened this issue Jun 2, 2024 · 1 comment · Fixed by #3620
Labels
bug Something isn't working

Comments

@TommyE123
Copy link
Contributor

Describe the bug
In release v7.9.0, the output formatting of the PowerShell error table when run in an Azure DevOps pipeline or Github Actions Job is now cut off. The table displaying linting results is not formatted properly, causing misalignment and truncation of information. I believe this issue was introduced by the changes in the following pull request: PR #3318.

Expected behavior
The linting results should be displayed in a properly formatted table with aligned columns and no truncation. Additionally, all columns (Severity, RuleName, ScriptName, Line, Message) should be fully visible.

Screenshots
V7.8.0
image

V7.11.1
image

Additional context

  • The Azure Devops log can support a much larger table width as it uses scroll bars. However id suggest if possible can we maybe just double the width as the message column can get rather long?

Thanks

@TommyE123 TommyE123 added the bug Something isn't working label Jun 2, 2024
@echoix
Copy link
Collaborator

echoix commented Jun 2, 2024

Can you try setting the env variable COLUMNS, and set it a little bit bigger? In the PR linked, the function called from shutils should respect it. It would give a preview of what the output would look like with a wider terminal, but would apply to all linters.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants