For readers of the future, this appeared to be broken even before this
PR was introduced but I couldn't pinpoint exactly where the breakage was
introduced
Signed-off-by: Petros Angelatos <petrosagg@gmail.com>
The photoslibrary API is not listed however is still available.
This adds a method of manually adding APIs to the shared.yaml and adds the photoslibary API info.
Fixes#198
Should remember it's not enough to just update the
api versions (major.minor.patch+X, where X is the API version)
as it is not enough to be a different version in the sense of
semver, for some reason.
That way we get rid of the duplication at least.
Probably it would be enough to just refer to version 1 of the
library respectively, and let semver do the rest.
Instead we link to the absolute location.
tech debt: we now use http://byron.github.io/google-apis-rs
multiple times and thus duplicate that information.
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 ?
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.
That way, it's easy to obtain the respective precompiled binary, as
well as seeing the source-code.
Overall, it makes promoting the tools easier as the CLI docs can be
linked directly.
Closes#108
[skip ci]
All assets are configured via shared.yaml and are located elsewhere in
the web. This could lead to broken assets at some point, but I am just
risking it for know, knowing that it's easily done to have local
resources.
Closes#106
[skip ci]
Previously we would define information about the program types
in two places, once for the index, and once per program type.
Now within the index.html, we just load the respective program type
information to have access to the latest at all times.
Closes#104
[skip ci]
That way, we can provide better service, as CLIs that consume a lot of
quota can easily have their own app credentials, and with it, their
own quota.
The fallback will be a project that allows to use all possible
google APIs.
The user can always put in his own application secret to use his own
quota or even paid services.
Fixes#80
