Adding stylish formatter to replace pretty formatter (deprecated) #1294
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We've spent a lot of time with the Pretty formatter, in multiple incarnations. The latest, which leverages the excellent Ink library, provides some pretty robust functionality, but sadly has also resulted in a lot of maintenance burden. The amount of benefit it gives is outweighed by the additional maintenance cost, all for a formatter.
As such, we're deprecating the pretty formatter and its associated infra (
@checkup/ui
package). This will be done in a follow up PR.To replace it, we're outputting the SARIF in a familiar format used by other static analysis tools, such as
eslint
andember-template-lint
.New
stylish
formatter:This formatter has a number of improvements over the pretty formatter: