New Minor Release

Signed-off-by: Mike Lischke <mike@lischke-online.de>

.vscodeignore

@@ -1,11 +1,19 @@
-.vscode/**
-.vscode-test/**
-out/test/**
-test/**
-src/**
-images/**
+.vscode/
+.vscode-test/
+.github/
+tests/
+src/
+images/
+grammars/
+doc/
+coverage/
 **/*.map
+
+cspell.json
+jest.config.js
+readme.md
 .gitignore
+.eslintignore
 tsconfig.json
 typings/**
 **/.antlr

cspell.json

@@ -18,6 +18,7 @@
         "chiki",
         "citi",
         "debugadapter",
+        "dendrogram",
         "deseret",
         "Deserialization",
         "duployan",

doc/graphical-visualizations.md

@@ -2,7 +2,7 @@
 
 This extension can create a number of graphical visualizations for you. All of them (except of the railroad/syntax diagram) share the same look and feel (they are all based on [D3.js](https://github.com/d3/d3)). You can press and hold the left mouse button in a free area in the graph and drag the mouse, to move the graph's view port. The mouse wheel or track pad can be used to zoom in and out. Certain graphs allow for additional actions, see below.
 
-All graphs also allow to export them to an SVG file (or in the case of the full RRD list, to an HTML file). The export will also copy the internal CSS file, as well as all custom CSS files you have specified for a graph type (in the settings). SVG files always use the light theme style colors, while the HTML output follows the currently set vscode theme.
+All graphs also allow to export them to an SVG file (and in the case of the full RRD list, also to an HTML file). The export will add the internal CSS file, as well as all custom CSS files you have specified for a graph type (in the settings) to the exported SVG. SVG files always use the light theme style colors, while the HTML output follows the currently set vscode theme.
 
 ## Railroad (aka. Syntax) Diagrams
 
@@ -22,5 +22,3 @@ In order to get an impression about the complexity of your grammar and visually
 
 The more lines you see, the higher the rules interact with each other. You can hover with the mouse over a rule name and it will highlight all relationships for that rule (while the rest is faded out). Red lines are drawn to callers of that rule, green lines for those called by it. Hence many red lines means this is a rule used by many others and hence a good candidate for optimization. Many green lines however indicate a high complexity and you should perhaps refactor this rule into multiple smaller ones.
 >![](https://raw.githubusercontent.com/mike-lischke/vscode-antlr4/master/images/antlr4-11.png)
-
-

package.json

@@ -7,7 +7,7 @@
         "color": "#2789e1",
         "theme": "dark"
     },
-    "version": "2.3.1",
+    "version": "2.4.0",
     "publisher": "mike-lischke",
     "license": "SEE LICENSE IN License.txt",
     "repository": {

readme.md

@@ -68,7 +68,23 @@ Bug fixing and what feels appealing to hack on.
 
 ## Release Notes
 
+### 2.4.0
+
+- Switched to a new TypeScript runtime (antlr4ng), which supports the latest features from ANTLR4 (e.g. case sensitive identifiers).
+- Fixed bug #195: Extension breaks if filename ends with Parser
+- Fixed bug #197: Use lexer token labels when generating tokens in debug console
+- Fixed bugs in the formatter (last token removal and wrong action with copy/paste).
+- Fixed a bug in the ATN graph renderer, where rule name + index were not properly updated, when navigating between rules.
+- Railroad diagrams received a big overhaul:
+  - Updated to latest version of the generation script.
+  - Added a button for exporting all diagrams in the all-rules list to individual SVG files.
+  - Added a new option to specify a character length in a line, after which an path is wrapped. This is useful for long alternatives.
+  - All CSS rules (including custom ones) are now inlined into exported SVG files, to avoid CSP problems.
+  - The all-rules list can now be filtered by typing a regular expression and only the visible diagrams are exported.
+  - A new option allows to strip out a part of rule names (e.g. a common `_SYMBOL` suffix), while rendering the SVG.
+
 ### 2.3.1
+
 A bug fix release for even stricter content security policies in VS Code starting at version 1.73.
 
 - Fixed bug #192: Broken Parse Tree Window on VSCode v1.73