Closed KristofferC closed 5 years ago
Copied from https://github.com/JuliaEditorSupport/julia-vscode/issues/242
I'm enjoying VSCode. The diagnostics that are generated are cool and very useful! But it would be nice to have some say in which issues were flagged and which weren't. For example, I like to write this:
starttextangle = the_angle - (theta/2) - lspacedangle/2
where there are some spaces around operators and some not. (I prefer my way, at the moment. Until that day comes when we all have to format our code "correctly" to some official standard... :))
So that particular rule could be optional...?
Similarly, the rule about commas; I prefer a space after a comma, but this warrants a warning:
polygonlist = Array{Point, 1}[]
even though that's obviously better with a space... :)
Is there a way? I can't think of a decent interface, though...
Some possible configurations:
ColumnLimit
: try to stay within these many columnsSpacesInTupleTypes
:Tuple{A, B}
orTuple{A,B}
ParenthesizeRanges
:a + b:c
->(a + b):c
BreakStringLiterals
etc.