Using `make update-json`, all json descriptions have been update.
Quite interesting to see that there are plenty of new ones which
are giving 404 when queried. An actual bug, or something I should
look into ?
The interactive flow requires to paste a code back into the
command-line, which does only work when it's cat'ed, but not
if it is pasted.
This should let it handle everything internally, which is
way more user-friendly.
Those don't compile, usually for trivial reason, which means
they come up with duplicate types, or have name-clashes.
If there is the need, this can be fixed.
This update fixes the build on stable, and allows builds
on nightly as usual.
The trick is to use the latest version of serde-codegen,
which keeps the syntex version internal, preventing clashes
between libraries that might have different requirements.
Previously it would fail as the built-in doc target in make
doesn't handle features at all.
Now these need to be taken into consideration though for it
to have a chance.
It seems due to a so far possibly unfiled bug, cargo fails to
get it's CWDs right.
Last verified with cargo 0.11.0-nightly (42bce5c 2016-05-17).
To reproduce, just put the deleted file back and run a build command,
such as
```bash
make drive3-cli-cargo ARGS=build --no-default-features --features=nightly
```
Fixes#149
Nightly is now supported, in theory, to allow not to use serde_codegen,
which currently has trouble to build thanks to an assertion error.
Nightly on the other hand suffers from being build with incorrect
feature-flags, which makes quasi_macros fail to build ... .
It seems all these serde versions interact with each other
in unforseen ways, so they will have to be in sync for it
to work. Its a shaky card-house I am building here,
and I don't like it at all.
Considering we kind-of hardcoded this authentication type anyway,
we now use the Auth-types provided by hyper 0.8.
The incentive here was the compiler telling us that there the
yup-oauth::Scheme type doesn't implement the hyper::authorization::Scheme
anymore, even though that clearly was the case. Also it couldn't be
reproduced in yup-oauth itself.
This will need some work to get correct again, so this is just a crude
patch to make it work again.
Previously the yaml version generation could fail if your system-python
didn't have yaml installed. Now the virtual env is used, which is
guaranteed to support yaml.
