Open jeremyfiel opened 11 months ago
I found a configurable rule is causing this behavior
rule/header-param-exists:
subject:
type: Parameter
property: in
where:
- subject:
type: Operation
property: parameters
assertions:
defined: true
assertions:
const: header
I was playing around with trying to find a solution to https://github.com/Redocly/redocly-cli/pull/1286
Thank you @jeremyfiel for reporting this!
@jeremyfiel so if you remove the configurable rule the formatting gets back to normal?
Yes, something with the reporting and the way this rule is written causes the invalid output
@RomanHotsiy I found this happens again with this new rule I was testing:
The formatting issue seems to be in both VSC and the cli output
rules:
rule/operation-tags-must-be-defined:
severity: error
subject:
type: Operation
assertions:
required:
- tags
@RomanHotsiy @tatomyr
I think I found the root cause of this formatting error. If I omit message
in the configurable rule, it creates this formatting error.
@jeremyfiel I think it has something to do with OS. On Mac I get correct problems' output formatting:
Do you use Windows?
I do use windows. But if you remove the message
property it doesn't give you incorrect formatting?
Yes, this is without the message
property.
What happened?
Recently, the VS Code output is not formatted correctly. I'm not sure exactly when it started, but it seems to have been from last week.. 03/10/23+
Screenshots
two diff examples of output from different files.
Additional context