-
Currently, dartdoc generates the version as plain text. On api.dart.dev, it would be nice if the version was a link to the versioned (permalink) variant of the page:
https://api.dart.dev/dart-ffi/d…
-
Should we be blocking upgrade critical severity api deprecations? Or should we allow that? Or should we prevent devs from setting critical severity for api deprecations.
----
copying comments fro…
-
Hi, me again :)
My docusaurus project has 3 versions, and I only want to generate the API for the latest one. I would like to leave older versions as they are.
If I don't add versioned APIs, I get t…
-
If we want to make changes to the API when the package is on CRAN it would be painful - but if we version the headers based on API, for cran releases, we could help with that. Alternatively we could s…
-
Currently our API just uses the existing web endpoints, which is bad for the obvious reason that it makes it difficult to change the responses to those endpoints, leaving API consumers without a clear…
kueda updated
9 years ago
-
Following the discussion in https://github.com/whitequark/ppx_deriving_yojson/pull/49, I'd like to look a adding some kind of versioned API to ppx_deriving. But I'd like to discuss the final picture b…
ghost updated
7 years ago
-
Benefits
- Users have one place to look
- We can add explanatory text around them with intra-doc links
- They are versioned with the API
epage updated
3 weeks ago
-
[This line][1] suggests that `ckanapi` doesn't support APIs with different versions, for example http://data.europa.eu/euodp/data/api/3 .
Does `RemoteCKAN` need a new parameter in the constructor t…
-
In preparation for a v1.0 release, I'd like to publish a versioned JSONSchema document that consumers may validate against (and also allow us to evolve our API over time). Part of our public API is th…
-
Currently the [Kibana test client](packages/kbn-test/src/kbn_client) allows passing custom headers when making a low-level request, but does not support specifying route versions when calling sub-clie…