Conversation
mkessler001
left a comment
There was a problem hiding this comment.
I added a small addon that re-analyzes open files when the settings change (e.g. line length is modified).
There is another commit marked as TODO, which comes with two test cases, which are currently failing (block comment, mistreated strings as comments).
I was thinking about the same direction, but didn't watch to add this feature. Maybe I thought in a wrong way, but once the file is formatted and you change the settings it could lead into wrong line lengths. If you add the "watching" feature just for the line length then it could be little bit inconsistent. Overall, what's the benefit of having this feature? |
I see a problem when users change settings. Without the update mechanism, they would need to restart VSCode (or at least reload the extensions) to apply the new settings. This is not an intuitive behavior. |
c869f94 to
ef6e925
Compare
ef6e925 to
a4e5850
Compare
…mments This option allows to exclude comments from line length diagnostics, basically warning won't be generated.
a4e5850 to
84edb81
Compare
mkessler001
left a comment
There was a problem hiding this comment.
Looks good to me. Just keep in mind that this is a breaking change since we moved enableWarnings to diagnostics.enableWarnings.
devicetree.enableWarnings->devicetree.diagnostics.enableWarningsenableWarningsunderdiagnostics