-
Notifications
You must be signed in to change notification settings - Fork 6k
add limited analysis options #17332
add limited analysis options #17332
Conversation
| width: width, | ||
| lineNumber: lineNumber, | ||
| left: left, | ||
| // TODO(yjbanov): I chose -1 value just to fix the analyzer warning. I don't know if it's the right value to pass. |
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 default is -1. No need for TODO. /cc @mdebbar
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.
Done.
mdebbar
left a comment
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.
| // TODO(yjbanov): I chose -1 value just to fix the analyzer warning. I don't know if it's the right value to pass. | ||
| endIndexWithoutNewlines: -1, |
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.
Any value is fine here since we don't use it for comparison in tests.
Yes, VSCode and IntelliJ pick up this file automatically, so all the lints will show up in your editor as you type. I cleaned up all code for these particular hints, so they should never come back. |
|
I meant the commented ones. |
|
Yeah, you can uncomment them but not commit the analysis_options.yaml changes. |
|
|
This reverts commit 5389159.
This time I'm starting without Cirrus. Will add Cirrus serpartely from code changes. This reverts commit 6d33ee1.

Starting with a minimal set of lints and hints. Will gradually expand this file until it's no longer necessary and we can use the global repository analysis_options.yaml.