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
Chore: use precalculated counts in codeframe formatter #8296
Conversation
LGTM |
|
||
formatter(code); | ||
|
||
assert.equal(chalkStub.yellow.bold.callCount, 0); | ||
assert.equal(chalkStub.red.bold.callCount, 1); | ||
}); | ||
|
||
it("should return bold yellow summary when there are only warnings", () => { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The diff is kind of misleading here. Just to clarify, this was not removed, it was moved up to a separate describe
section above.
Hmm, I'm not sure I understand why
|
I think we should be able to ignore it. Since branch build completed on both appveyor as well as travis. |
What is the purpose of this pull request? (put an "X" next to item)
[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofixing to a rule
[ ] Add a CLI option
[ ] Add something to the core
[x] Other, please explain:
Chore. See below.
What changes did you make? (Give an overview)
Updated the codeframe formatter to use the precalculated error and warning counts, just like it was done in #8251.
Is there anything you'd like reviewers to focus on?
I think not!