stevedlawrence commented on code in PR #117:
URL: https://github.com/apache/daffodil-vscode/pull/117#discussion_r883874943
##########
package.json:
##########
@@ -63,24 +75,42 @@
"webpack-cli": "^3.3.12"
},
"main": "./dist/ext/extension.js",
- "browser": "./dist/web/extension.js",
"activationEvents": [
+ "onLanguage:dfdl",
"onDebugResolve:dfdl",
"onDebugDynamicConfigurations:dfdl",
"onCommand:extension.dfdl-debug.getProgramName",
"onCommand:extension.dfdl-debug.getDataName",
"onCommand:extension.dfdl-debug.runEditorContents",
"onCommand:extension.dfdl-debug.debugEditorContents",
- "onCommand:launch.config"
+ "onCommand:launch.config",
+ "onCommand:data.edit",
+ "onCommand:omega_edit.version",
+ "onCommand:toggle.experimental"
],
"workspaceTrust": {
"request": "never"
},
"contributes": {
- "snippets": [
+ "languages": [
{
- "language": "xml",
- "path": "./snippets/dfdl.json"
+ "id": "dfdl",
+ "aliases": [
+ "dfdl",
+ "dfdl"
+ ],
+ "extensions": [
+ ".xsd",
+ ".xml"
Review Comment:
I think infosets should just be treated like normal XML files.
If you wanted to get really fancy, you could have autocomplete editing of
infosets generated from DFDL schemas. I mentioned in another comment that there
are extensions out there that seem to be able to do this already with XSD's,
and since DFDL schemas are just normal XSD as far as infosets are aware,
something like that should work in theory.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
