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
At times, ESLint emits a message with no `ruleId`, indicating an internal
error in ESLint. Represent this in SARIF as a `toolExecutionNotification`
with `level: "error"`, rather than as a `result` with no `ruleId`, which is
invalid.
This affects some unit tests, which now must always provide a `ruleId`.
Also:
- Per the spec, emit `run.results` even if the array is empty, as a
positive indicator that the tool found no results. This affects the
unit test which previously expected `run.results` to be `undefined`
in this case.
Specifically, we do not always provide the rule ID, e.g.,
The text was updated successfully, but these errors were encountered: