Closed vemonet closed 3 years ago
Hey @vemonet!
The reason JSON files are parsed is because queries can be expressed as JSON. You are right, this could be confusing for other standard files such as you mention.
As a work around, what you could do is have your queries on their own directory, for example:
https://grlc.io/api-git/c-martinez/shapes-of-you/subdir/queries
Would this work for you?
Yes that works for my use-case, thanks for the suggestion, it is cleaner anyway as the API grows :)
Hi, I deployed a grlc OpenAPI alongside a React TypeScript app. See the repository here: http://grlc.io/api-git/vemonet/shapes-of-you it's a small project to index and expose SHACL/ShEx shapes, OWL/OBO ontologies, SKOS vocabularies and SPARQL queries, I reused some concepts, metadata and even code bits from grlc.io for the SPARQL part, thanks a lot!
The API works, but it takes some time to load and shows a few warning due to unvalid JSON (which are required for my typescript project). In this case
package.json
,tsconfig.json
andapp.json
You should be able to check it yourself here: http://grlc.io/api-git/vemonet/shapes-of-you
Would it be possible to disable the display of warning in case a JSON file is not parser properly? It is a relatively common file to have at the root of a repository :)