Skip to content

Conversation

0xrusowsky
Copy link
Contributor

Motivation

ref:

Solution

track emitter kind in LintContext and avoid ANSI chars when necessary

Copy link
Member

@DaniPopes DaniPopes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we add a snapshot test?

@0xrusowsky 0xrusowsky requested a review from DaniPopes August 29, 2025 08:32
@0xrusowsky
Copy link
Contributor Author

@onbjerg can u confirm that this stderr output is the one u expect?

@0xrusowsky 0xrusowsky requested a review from DaniPopes August 29, 2025 10:16
@0xrusowsky 0xrusowsky merged commit 56aadcb into master Aug 29, 2025
23 checks passed
@0xrusowsky 0xrusowsky deleted the rusowsky/lint-no-ansi branch August 29, 2025 11:31
@github-project-automation github-project-automation bot moved this to Done in Foundry Aug 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

forge lint --json has ANSI escape sequences in messages
2 participants