I don't really need to have brace matching at the namespace and class level, as usually, these are not "nested", which is where an extension like this really shines: the nesting of anonymous objects and lambda functions and their attendant parens. and braces, or even if statements and potentially complex conditionals.
It may be a good idea to provide an option to disable brace matching from occurring at those levels. Maybe even two options, one for each, where the default value is True:
It's an interesting idea, but not very likely I'll implement this, since Viasfora does not do semantic parsing of the document, so it has no clue what a namespace or class is at all.
I don't really need to have brace matching at the namespace and class level, as usually, these are not "nested", which is where an extension like this really shines: the nesting of anonymous objects and lambda functions and their attendant parens. and braces, or even
if
statements and potentially complex conditionals.It may be a good idea to provide an option to disable brace matching from occurring at those levels. Maybe even two options, one for each, where the default value is True:
namepsace
brace matchingclass
brace matching