package.json fix? #378
package.json fix? #378
Conversation
Files like profileFormText.ttl may show up gray without proper syntax highlighting in code editors. For VSCode, I needed an extension. Just adding a suggestion so a new comer or someone playing around with SPARQL and RDF related things, doesn't think they have to operate completely in gray colored code!
| If you have trouble seeing syntax highlighting for SPARQL, Turtle, TriG, N-Triples, N-Quads, etc... | ||
| Try installing an extension! For VSCode, there are many, but a great one is RDFox Syntax Highlighting. |
There was a problem hiding this comment.
| If you have trouble seeing syntax highlighting for SPARQL, Turtle, TriG, N-Triples, N-Quads, etc... | |
| Try installing an extension! For VSCode, there are many, but a great one is RDFox Syntax Highlighting. | |
| If you have trouble seeing syntax highlighting for SPARQL, Turtle, TriG, N-Triples, N-Quads, etc., | |
| try installing an extension! For VSCode, there are many; one that we've used is | |
| [RDFox Syntax Highlighting](https://marketplace.visualstudio.com/items?itemName=rdfox.rdfox-rdf). |
| @@ -10,7 +10,7 @@ | |||
| "build-lib": "npm run build-form && babel src -d lib --source-maps --extensions '.ts,.js'", | |||
| "build-dev": "webpack --progress --mode=development", | |||
| "build-types": "tsc --emitDeclarationOnly", | |||
| "build-version": "./timestamp.sh > src/versionInfo.ts && eslint 'src/versionInfo.ts' --fix", | |||
There was a problem hiding this comment.
This replaces whatever the build-version script did before by calling timestamp.sh with just a call to eslint. Does not seem right to me.
There was a problem hiding this comment.
Not sure as to why VSCode throws off that error, but in the mean time, perhaps we could use it as a cautionary suggestion to Windows 10 users? If it doesn't seem right, then maybe it is not. Should the suggestion instead go the readme?
There was a problem hiding this comment.
Currently the dev setup seems not to be Windows compatible. At least the timestamp.sh would need to change if we want to make the build run under windows. There might be more changes needed. Under Windows you could try using WSL.
On Windows 10 in VSCode, solid-panes will not start and will give you a ./ error, unless you revise the following from
"./timestamp.sh > src/versionInfo.ts && eslint 'src/versionInfo.ts'
to
"build-version": "eslint --fix",