Please check if what you want to add to awesome-go list meets quality standards before sending pull request. Thanks!
Please provide package links to:
repo link :
- https://github.com/root-gg/plik/tree/master
live demo :
- https://plik.root.gg/#/
pkg.go.dev:
- https://pkg.go.dev/github.com/root-gg/plik
goreportcard.com:
- https://goreportcard.com/report/github.com/root-gg/plik
coverage service link (codecov, coveralls, gocover etc.):
Can't get any of them to work but coverage is displayed in every build :
https://github.com/root-gg/plik/runs/4300158864
ok github.com/root-gg/plik/plik 10.153s coverage: 90.1% of statements
ok github.com/root-gg/plik/server/common 50.332s coverage: 87.0% of statements
ok github.com/root-gg/plik/server/context 0.050s coverage: 25.3% of statements (automatically generated accessors)
ok github.com/root-gg/plik/server/data/file 0.046s coverage: 89.5% of statements
ok github.com/root-gg/plik/server/data/stream 0.084s coverage: 100.0% of statements
ok github.com/root-gg/plik/server/data/testing 0.040s coverage: 96.4% of statements
ok github.com/root-gg/plik/server/handlers 65.720s coverage: 83.9% of statements
ok github.com/root-gg/plik/server/metadata 8.501s coverage: 82.1% of statements
ok github.com/root-gg/plik/server/middleware 0.298s coverage: 90.2% of statements
ok github.com/root-gg/plik/server/server 2.103s coverage: 75.9% of statements
Tests are also run against compatible backends using Docker images (see the test-backends step)
Make sure that you've checked the boxes below before you submit PR: not every repository (project) will fit into every option, but most projects should
I have added my package in alphabetical order. YES
I have an appropriate description with correct grammar. YES
I know that this package was not listed before. YES
I have added pkg.go.dev link to the repo and to my pull request. YES
I have added coverage service link to the repo and to my pull request. See above
I have added goreportcard link to the repo and to my pull request. YES
I have read Contribution guidelines, maintainers note and Quality standard. YES
Thanks for your PR, you're awesome! 👍
No YOU are awesome :)
The library is currently on `v0.6.0` and is already used in production for several
products by OTA-Insight. We aim to have to be on a stable version in the near future.
In order to do so we are waiting on:
- the stabilisation of the Storage API used for one of three possible clients under the hood;
- opt-in data write error handling with managed retry: decide whether we want it or not, and if so, lock this into the API;
