feat: add antlr-ng tool support#108
Merged
kaby76 merged 1 commit intokaby76:masterfrom Jan 13, 2026
Merged
Conversation
Implements kaby76#92 by adding Node.js-based antlr-ng as alternative to Java ANTLR4 tool with full backward compatibility. Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com> Signed-off-by: JobaDiniz <joberto.diniz@netdocuments.com>
JobaDiniz
force-pushed
the
feature/antlr-ng-support
branch
from
37f1933 to
d15b151
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR implements #92 by adding support for antlr-ng as an alternative ANTLR tool. The implementation uses a pluggable architecture with an IAntlrTool interface, allowing users to choose between the Java-based ANTLR4 tool (default) or the Node.js-based antlr-ng tool via the
<ToolType>MSBuild property. Both tools share the same configuration options and work seamlessly within the existing build pipeline, with antlr-ng providing the benefit of not requiring a Java runtime. The implementation includes automatic Node.js and antlr-ng discovery, proper C# code generation with language target auto-detection, and a complete test suite validating the integration.