You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+22
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,11 @@
1
1
Thank you very much for your interest in contributing to grlc! It's people like you that truly make the Semantic Web more accessible to everyone :)
2
2
3
+
## Communication channels
4
+
5
+
If you would like to get in touch with the grlc developers, and with other users of grlc, you can reach us in two ways:
6
+
- Via Twitter, by using the grlc handle (**@grlcldapi**). Follow this account to hear about updates.
7
+
- Via the grlc [mailing list](https://groups.google.com/g/grlc-list/). Sign up to the mailing list to ask questions and make suggestions.
8
+
3
9
## Filing bug reports
4
10
5
11
The official channel to file bug reports is via our GitHub's [issue tracker](https://github.com/CLARIAH/grlc/issues). When doing so make sure that:
@@ -17,6 +23,14 @@ As with bug reports, for requesting features please use the [issue tracker](http
17
23
- Name the file/module if known/available
18
24
- Tag the issue as **enhancement**
19
25
26
+
## Sending pull requests
27
+
28
+
If you would like to contribute to the code directly, please send in a [pull request (PR)](https://github.com/CLARIAH/grlc/pulls). Please make sure that:
29
+
- The title of your PR briefly describes the content
30
+
- Describe in detail what your PR contributes
31
+
- If your PR addresses a specific issue, indicate the issue number
32
+
- Assign @albertmeronyo or @c-martinez as reviewer of your PR.
33
+
20
34
## Testing environment
21
35
22
36
To get started with hacking grlc, follow these steps to create a local testing environment (you'll need [docker](https://www.docker.com/) and [docker-compose](https://docs.docker.com/compose/)):
@@ -46,6 +60,14 @@ services:
46
60
47
61
You're good to pick any issue at the [issue tracker](https://github.com/CLARIAH/grlc/issues) marked as **enhancement** and start implementing it :)
48
62
63
+
## Governance model
64
+
65
+
As creators of grlc, [@albertmeronyo](https://github.com/albertmeronyo) and [@c-martinez](http://github.com/c-martinez) are benevolent dictators for this project. This means that they have a final say of the direction of the project. This DOES NOT mean they are not willing to listen to suggestion (on the contrary, they *love* to hear new ideas)!
66
+
67
+
## Contributing
68
+
69
+
All grlc contributors will be listed in the [CONTRIBUTORS.md](CONTRIBUTORS.md) file. Also, [notes of new releases](https://github.com/CLARIAH/grlc/releases) will mention who contributed to that specific release.
70
+
49
71
## Questions
50
72
51
73
Please open an issue at the [issue tracker](https://github.com/CLARIAH/grlc/issues) and tag it as **question**
The API paths of all location types point to the generated [swagger-ui](https://swagger.io/) style API documentation. On the API documentation page, you can explore available API calls and execute individual API calls.
105
105
106
-
You can also view the swagger spec of your API, by visiting `<API-path>/spec/`, for example: `http://grlc.io/api-git/CLARIAH/grlc-queries/spec/`
106
+
You can also view the swagger spec of your API, by visiting `<API-path>/swagger`, for example: `http://grlc.io/api-git/CLARIAH/grlc-queries/swagger`
107
107
108
108
### grlc query execution
109
109
When you call an API endpoint, grlc executes the SPARQL query for that endpoint by combining supplied parameters and decorators.
@@ -192,6 +192,17 @@ Syntax:
192
192
193
193
Example [query](https://github.com/CLARIAH/grlc-queries/blob/master/tags.rq) and the equivalent [API operation](http://grlc.io/api-git/CLARIAH/grlc-queries/#/group1/get_tags).
194
194
195
+
### `defaults`
196
+
Set the default value in the swagger-ui for a specific parameter in the query.
197
+
198
+
Syntax:
199
+
```
200
+
#+ defaults:
201
+
#+ - param_name: default_value
202
+
```
203
+
204
+
Example [query](https://github.com/CLARIAH/grlc-queries/blob/master/defaults.rq) and the equivalent [API operation](http://grlc.io/api-git/CLARIAH/grlc-queries/#/default/get_defaults).
205
+
195
206
### `enumerate`
196
207
Indicates which parameters of your query/operation should get enumerations (and get dropdown menus in the swagger-ui) using the given values from the SPARQL endpoint. The values for each enumeration variable can also be specified into the query decorators to save endpoint requests and speed up the API generation.
197
208
@@ -218,7 +229,7 @@ Syntax:
218
229
Example [query](https://github.com/CLARIAH/grlc-queries/blob/master/endpoint_url.rq) and the equivalent [API operation](http://grlc.io/api-git/CLARIAH/grlc-queries/#/default/get_endpoint_url).
219
230
220
231
### `transform`
221
-
Allows query results to be converted to the specified JSON structure, by using [SPARQLTransformer](https://github.com/D2KLab/py-sparql-transformer) syntax.
232
+
Allows query results to be converted to the specified JSON structure, by using [SPARQLTransformer](https://github.com/D2KLab/py-sparql-transformer) syntax. Notice that the response content type must be set to `application/json` for the transformation to take effect.
222
233
223
234
Syntax:
224
235
```
@@ -351,7 +362,7 @@ Check our [contributing](CONTRIBUTING.md) guidelines for these and more, and joi
351
362
352
363
If you cannot code, that's no problem! There's still plenty you can contribute:
353
364
354
-
- Share your experience at using grlc in Twitter (mention the handler **@grlcldapi**)
365
+
- Share your experience at using grlc in Twitter (mention the handle **@grlcldapi**)
355
366
- If you are good with HTML/CSS, [let us know](mailto:albert.meronyo@gmail.com)
0 commit comments