-
Change `class!`, `methods!` and `unsafe_methods!` macro to have a better API for defining Ruby classes (needs discussion and decision).
-
Currently, we have to manually keep the following file in sync with the actual definitions of the public API:
https://github.com/gradle/gradle/blob/57cc16c8fbf4116a0ef0ad7b742c1a4a4e11a474/.idea/scop…
-
### Package name
core
### Package version
11.0.4
### Reproduction steps
Create an API specification (json or yaml format) containing an endpoint with a parameter whose name contains '['…
-
Currently `parameters` in tool definition is a very limited subset of a JSON Schema. This makes it non-compatible with OpenAI (https://github.com/ollama/ollama/issues/6155) and it general it makes it …
mitar updated
2 weeks ago
-
# Support OpenAPI Specification
We need to implement OpenAPI support in the ebrick framework to standardize API documentation and provide integration for client-side tools and services.
## Require…
-
### Describe the feature you would like to see added
Component methods are not current documented in the API docs, e.g., `show` and `hide` methods of AutoComplete can only be known by looking at the …
-
[Section 12.2](http://docs.ogc.org/DRAFTS/19-072.html#api-definition) says that
> Every API implementation should provide an API Definition resource that describes the capabilities provided by that A…
-
The Currently datapre-redis microservice uses the 3 REST API for:
1. Upload file: `/v1/dataprep`
2. Get file: `/v1/dataprep/get_file`
3. Delete file: `/v1/dataprep/delete_file`
And these 3 API…
-
OGC API Standards are expected to target OpenAPI 3.0.
Part 1 of the OGC API - Connected Systems candidate Standard correctly mentions only OpenAPI 3.0.
https://docs.ogc.org/DRAFTS/23-001r0.html
…
-