From 79e0e5b6f5d67509617ed998188ea98ce28c9078 Mon Sep 17 00:00:00 2001 From: Carlos Martinez Date: Mon, 19 Aug 2024 22:39:50 +0200 Subject: [PATCH] Add a mention of query-in-json support --- README.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/README.md b/README.md index 6acf461..069a953 100644 --- a/README.md +++ b/README.md @@ -43,6 +43,8 @@ Your queries can add API parameters to each operation by using the [parameter ma Your queries can include special [decorators](#decorator-syntax) to add extra functionality to your API. +grlc also supports SPARQL queries expressed as json, using the [SPARQL Transformer](https://github.com/D2KLab/py-sparql-transformer) [Query in JSON](https://github.com/D2KLab/sparql-transformer/blob/master/README.md#query-in-json) syntax. (**Tip**: the [SPARQL Transformer Playground](https://d2klab.github.io/sparql-transformer/) is very useful when building queries with this syntax). + ### Query location grlc can load your query collection from different locations: from a GitHub repository (`api-git`), from a GitLab repository (`api-gitlab`), from local storage (`api-local`), and from a specification file (`api-url`). Each type of location has specific features and is accessible via different paths. However all location types produce the same beautiful APIs.