cookie-cutter
cookie-cutter copied to clipboard
An opinionated micro-services framework for TypeScript
A service that only wants to serve read-requests currently still needs a key that has read+write permissions, because the `CosmosClient` on initialization is trying to create the stored procedures in...
We'd like to materialize out event streams to blob storage instead of Cosmos. We wrote our own custom provider/sink but it would be nice to be part of cookie-cutter
There a few different intermittent errors that have a tendency to pop up when using cc-gpc. ``` {"log":{"time":"2019-10-04T14:58:42.716Z","level":"EROR","ctx":"XXX","fields":{"msg":["failed to dispatch message"],"type":["SomeEvent"],"err":["Backend Error"],"stack":["Error: Backend Error at Util.parseHttpRespBody (/usr/src/node_modules/@google-cloud/common/build/src/util.js:194:38) at Util.handleResp (/usr/src/node_modules/@google-cloud/common/build/src/util.js:135:117)...
The documentation should be able to switch between all published stable versions and the current beta version. Once multiple versions are supported we should also switch publishing the docs from...
Docusaurus supports searching the documentation via Algolia DocSearch. We should enable that feature. See https://docusaurus.io/docs/en/search for details.
The documentation for Optimistic Concurrency is currently missing and the link to the page is broken.
It seems that one can assert exception by inspecting the `responses` field of the result of `runIntegrationTest` for error. It's not obvious how it's done. We should update the documentation...
Ensure the documentation for each module contains a section that has an exhaustive list of all available metadata key/value pairs.
Error Handling Modes are currently not covered by the documentation at all.
Since ts-lint is deprecated and not maintained anymore, we should switch to [`typescript-eslint`](https://github.com/typescript-eslint/typescript-eslint).