Otherwise it's possible to leave bytes related to a previous version
of the file in tact, tailing the newly written content.
This in turn leads to malformed json when tokens are rewritten.
This seemed easiest, especially since I also am the author of
pulldown-cmark-to-cmark :D.
Funny how things fit together sometimes. And so much better than
if I would have tried the same in pure python.
For some reason, 'docs-v1' JSON file wasn't present in the repo, and
thus makefile couldn't be generated from scratch.
Now we just ignore this particular error.
change `remove_json_null_values()` to properly remove nulls from and recurse in to arrays
google_firestore1_beta1's `CommitRequest` contains an array of `Write` objects which can ultimately
contain `Value` members that need to have nulls removed to avoid sending multiple types of values
which generates a 400 response
fixes calls to google_firestore1_beta1's `hub.projects().databases_documents_commit()`
Sort and format JSON files to remove/minimise any diffs between
update-json runs. This also acts as a JSON validator to error when the
downloaded JSON file has been truncated.
In the section that describes setting up the Cargo.toml, add the
required dependencies, and note that `hyper` and `hyper-rustls` are not
the latest versions. This helps new users get started quicker and
easier.
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
This is backwards compatible, but allows `add_scope(None)` as well.
Maybe it's better to just add another function, but on the other hand,
this would already do and solves that somewhat more special case.
Related to #172
Summary of changes:
- Converted from using span + br tags for formatting to using tables
- Added Bootstrap stylesheet
- Refactored a lot of the logic which was being done in the html ${...}
tags out into a block which gets run at the start of each api version.
(hopefully this will make the template easier to maintain in the long
run)
Possible issue:
I swapped from looping over each key in `tc.keys()` to assuming the keys
will only ever be ["api", "cli"]. This hard codes the keys instead of
getting them dynamically, but makes it easier to format as a table and
lets you pull a lot of the logic out of the template and into a single
block before each table row.
If the types of application in `tc.keys()` ever changes then this
template will need to be updated accordingly!
