You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
V7.11.1
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
The text was updated successfully, but these errors were encountered:
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.
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
V7.11.1
Additional context
Thanks
The text was updated successfully, but these errors were encountered: