-
Hi all,
Are there any plans for built-in API-versioning? I've been looking at https://github.com/dingo/api, and it looks great, though a little overkill for what I need. One thing it does have it sma…
snipe updated
8 years ago
-
Yo, so you should put some proper semantic version numbers on this thing so that people can keep their bindings up to date.
-
It's time to start thinking about real [semantic versioning](http://semver.org) and real release cycles.
I still want to release frequently to fix occassional bugs - right now it's all uncontrolled t…
-
See https://github.com/theodi/shared/issues/484
-
Just an idea for myself for potential mapping for versioning:
Currently, mapping is defined using Resource and Collection annotations:
``` php
/**
* @REST\Resource(controller="MyController")
* @RE…
-
For documentation at http://socrata.github.io/datasync/ consider adopting better version documenting. Currently the documentation is just continually updated, presumably kept up to match the newest re…
-
I think this distracts from the rest of 1.0 so spinning it off into its own issue from #426
The question is not whether semantic versioning isn't helpful in theory. The question is what happens in p…
-
How to do API versioning? Is there a documentation about this?
-
BMI doesnt have any way to tell which version is currently deployed. This can be resolved by adding a build number or version number in the cli.
-
### 🔍 Search Terms
`semantic versioning`
### ✅ Viability Checklist
- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of…