-
This is perhaps already somewhere on the dev & roll-out roadmap: would adding explicit URL-based API versioning no be sensible, as a future-proofing measure?
I am aware that there is versioning suppo…
-
There is another project focused on providing versioned OData APIs for different versions of .NET Web API across .NET and .NET Core here:
https://github.com/microsoft/aspnet-api-versioning
I had o…
-
Now that we can remove the binary protocol and the http API is used by both tray, it might be a good idea to introduce versionned API.
The proposition is to copy the current http API under /v1 for…
-
## Description
In the past almost with each version (also patch versions) breaking API changes were introduced in the EDC. This hurts a lot and creates a lot of efforts while adopting patched or ne…
-
Our project is introducing CRDs. We'd like to make we use a consistent process of introducing CRDs and versioning them, which both our users and developers understand.
Add a document that answers the…
-
We discussed this in the last community meeting, in the context of now having a release process for `obsctl` (https://github.com/observatorium/obsctl/pull/26).
There were couple of ideas floating a…
-
Everything worked great for a model. When it came to an array/collection of models, this is where I'm stuck and I wonder if it has to do with the fact my Rails API project is versioned (ie: v1, v2)?
…
-
-
## 🚀 Feature
When implementing a new out-of-source ATen backend extension for PyTorch, we find ATen operator APIs are incompatible from version to version (even among minor versions, for example v1…
-
Potential solutions:
- [speakeasyapi.dev](speakeasyapi.dev)
- [stainlessapi.com](stainlessapi.com)
- Liblab
Note: Liblab doesn't integrate with our documentation system
Requirements:
Base URL cust…