-
Notifications
You must be signed in to change notification settings - Fork 82
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
Add LemMinx extensions via vscode user settings #251
Comments
+1, this is the VSCode equivalent of the lemminxExtension in Wild Web Developer (although simpler for non-VSCode developers to use). |
@angelozerr how hard do you think it would be for someone who has never wrote (but has read a lot of) TypeScript :) Maybe I should try to fix this bug in my spare time. |
I think it's not a big deal. The idea is to
like Line 87 in e01d3e0
vscode-xml/src/javaServerStarter.ts Line 66 in e01d3e0
@fbricon for the settings name I suggest |
@AObuchow is there any chance that you work on this issue? I think it could be a nice feature to test quickly the LemMinx maven support inside vscode. |
Wow I was just thinking about this yesterday night, good timing @angelozerr ;) I’ll see with my team how much of a priority this is. It might be that I’ll work on it in my spare time. I’m about to release my first Eclipse plugin on the marketplace (probably tomorrow) but after that I want to get this done :) |
Adds a new setting `xml.extension.jars`, where you can list jars to contribute to the LemMinX classpath. You can use this feature to test LemMinX extensions in VSCode. Closes redhat-developer#251 Signed-off-by: David Thompson <[email protected]>
Adds a new setting `xml.extension.jars`, where you can list jars to contribute to the LemMinX classpath. You can use this feature to test LemMinX extensions in VSCode. Closes redhat-developer#251 Signed-off-by: David Thompson <[email protected]>
Adds a new setting `xml.extension.jars`, where you can list jars to contribute to the LemMinX classpath. You can use this feature to test LemMinX extensions in VSCode. Closes redhat-developer#251 Signed-off-by: David Thompson <[email protected]>
Adds a new setting `xml.extension.jars`, where you can list jars to contribute to the LemMinX classpath. You can use this feature to test LemMinX extensions in VSCode. Closes redhat-developer#251 Signed-off-by: David Thompson <[email protected]>
Adds a new setting `xml.extension.jars`, where you can list jars to contribute to the LemMinX classpath. You can use this feature to test LemMinX extensions in VSCode. Closes redhat-developer#251 Signed-off-by: David Thompson <[email protected]>
Adds a new setting `xml.extension.jars`, where you can list jars to contribute to the LemMinX classpath. You can use this feature to test LemMinX extensions in VSCode. Closes redhat-developer#251 Signed-off-by: David Thompson <[email protected]>
Adds a new setting `xml.extension.jars`, where you can list jars to contribute to the LemMinX classpath. You can use this feature to test LemMinX extensions in VSCode. Closes redhat-developer#251 Signed-off-by: David Thompson <[email protected]>
Adds a new setting `xml.extension.jars`, where you can list jars to contribute to the LemMinX classpath. You can use this feature to test LemMinX extensions in VSCode. Closes redhat-developer#251 Signed-off-by: David Thompson <[email protected]>
Adds a new setting `xml.extension.jars`, where you can list jars to contribute to the LemMinX classpath. You can use this feature to test LemMinX extensions in VSCode. Closes #251 Signed-off-by: David Thompson <[email protected]>
LemMinx is extensible to manage custom completion, validation, etc. https://github.com/eclipse/lemminx-maven is a good sample of extension which provides support for maven.
To use this extension, it requires to create a vscode extension (eg: https://github.com/angelozerr/vscode-xml-maven)
This issue is to provide a new xml settings like
xml.extension.jars
which is an array of String which defines paths from LemMinx JAR extensions. to use when classpath is createdThe text was updated successfully, but these errors were encountered: