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
Currently, file-level lint warnings are not reported by the plugin. To fix, we should make the following changes:
BufIssue.toTextRange returns null if the start/end offsets are equal, which file-level lint warnings are (they're reported with start/end line and start/end column all set to 1). We should detect thse any report annotations as fileLevel() instead of range(...).
The IgnoreBufIssueQuickFix can't be used to ignore these lint failures for these types of errors. We should instead update the buf.yaml config file with https://buf.build/docs/configuration/v1/buf-yaml#ignore_only or come up with another appropriate fix.
This affects the following types of lint warnings:
Currently, file-level lint warnings are not reported by the plugin. To fix, we should make the following changes:
BufIssue.toTextRange
returns null if the start/end offsets are equal, which file-level lint warnings are (they're reported with start/end line and start/end column all set to 1). We should detect thse any report annotations asfileLevel()
instead ofrange(...)
.IgnoreBufIssueQuickFix
can't be used to ignore these lint failures for these types of errors. We should instead update thebuf.yaml
config file with https://buf.build/docs/configuration/v1/buf-yaml#ignore_only or come up with another appropriate fix.This affects the following types of lint warnings:
The text was updated successfully, but these errors were encountered: