From 6826ce3934d8e780bc50b7631d959f79eaafa98f Mon Sep 17 00:00:00 2001 From: Scott Wells Date: Fri, 6 Dec 2024 09:21:30 -0600 Subject: [PATCH] Changed the TODO into a clear note about the assumption being made for future maintainers. --- .../lsp4ij/features/foldingRange/LSPFoldingRangeBuilder.java | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/src/main/java/com/redhat/devtools/lsp4ij/features/foldingRange/LSPFoldingRangeBuilder.java b/src/main/java/com/redhat/devtools/lsp4ij/features/foldingRange/LSPFoldingRangeBuilder.java index 76577271d..08d007825 100644 --- a/src/main/java/com/redhat/devtools/lsp4ij/features/foldingRange/LSPFoldingRangeBuilder.java +++ b/src/main/java/com/redhat/devtools/lsp4ij/features/foldingRange/LSPFoldingRangeBuilder.java @@ -48,7 +48,9 @@ public class LSPFoldingRangeBuilder extends CustomFoldingBuilder { private static final Logger LOGGER = LoggerFactory.getLogger(LSPFoldingRangeBuilder.class); - // TODO: Can this be derived from the language server? If not, these are the standard for modern languages + // NOTE: JetBrains has maintained a long assumption that these are the primary structural block delimiters via + // AbstractFileType's explicit support for them. If/when other structural block delimiters are discovered for + // languages supported by LSP, we can revisit this hard-coded assumption. private static final Map BRACE_PAIR_CHARS_FWD = Map.of( '{', '}', '[', ']',