Experiments for language injection support for VADL - #5
Draft
rascmatt wants to merge 1 commit into
Draft
Conversation
Collaborator
|
Awesome 👍 |
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
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.
@flofriday
Here's the current/final state of my experiments to support language injection for VADL. Feel free to modify, or abandon the PR.
Fyi if you're interested, I invited you to the plugin repo where I used the Coco/R generated scanner to integrate IntelliJ syntax highlighting & language injections: https://github.com/rascmatt/tifl-plugin
Originally I thought that adding the
VadlLanguageandVadlFileTypewould be enough, but it turns out that language injection seems to only work in combination with an implementation of IntelliJ's PSI framework.I also tried to comply by providing a 'dummy' lexer & parser, and even tried a custom language injector, but without success. Intellj just ignores the LSP in these scenarios.