-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: multiple extensions for single language #344
Feature: multiple extensions for single language #344
Conversation
rascal-lsp/src/main/java/org/rascalmpl/vscode/lsp/terminal/ITerminalIDEServer.java
Outdated
Show resolved
Hide resolved
rascal-lsp/src/main/java/org/rascalmpl/vscode/lsp/parametric/ParserOnlyContribution.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
necessary and efficiently solved. Do our tests cover all the cases we've changed here? And do we have a test for the multiple-extension situation?
Thanks. Well, I updated the pico example to use the new constructor. And the test fail, but that's just UI test jank, since only the first DSL test fails. In general there is not difference between how a language with 1 extension or more is handled now. |
Right. So if the tests work, then we are sure of that. But we should add a test for a language with two extensions right? Otherwise, this feature will break the next time someone does something "quickly". Like me :-) |
that seems wise, I added a test for it. |
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
As discussed in #343 we want to better align with LSP & VS Code by allowing multiple extensions for a single language.
The biggest change was in our multiplexer, which used to work by extension alone, but now maps extensions to language, and then continues as before.
I've tested that the old DSLs still work without requiring changes.