[go] Allow user-defined Logger
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- go
- Domain
- api, backend-api-design
Research direction
No files or tests are named. Start by reviewing the Go codebase, especially the NATS Client wrapper and generated bindings, and trace how logging is currently exposed. Done means users can pass custom loggers through the API and use them in both integration points, with the expected interface and scope clarified first.
Written by the indexing model from the issue text.
Description
The Go ecosystem has a lot of opinionated logger, slog is indeed the one proposed by the standard library, it is good for general-purpose application but may fall short for high-performance applications.
If you are okay with that, I may contribute to wRPC Go codebase by allowing users to pass custom Loggers using the API of https://github.com/go-logr/logr so they integrate better with:
- The NATS Client wrapper,
- The generated bindings,
WDYT?
- Dominant language
- Rust
- Stars
- 336
- Forks
- 48
- Avg merge
- 10h 39m
- Merged PRs (30d)
- 203
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bytecodealliance/wrpc
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
bytecodealliance/wrpc#1785 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
bytecodealliance/wrpc#1701 ·
Maintainers usually reply within 1 day
-
generate wrpc-server based on wit-bindings and homogenize the wrpc-client and wasmtime-bindingsOpen
Difficulty 5/5 Over a week Newbie friendliness 35/100
bytecodealliance/wrpc#1424 · 1 reaction ·
Maintainers usually reply within 1 day
-
add map supportOpen
Difficulty 4/5 3-5 days Newbie friendliness 35/100
bytecodealliance/wrpc#1151 ·
Maintainers usually reply within 1 day
-
wRPC protocol v0.1.0Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
bytecodealliance/wrpc#494 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
All issues in bytecodealliance/wrpc
Similar issues
-
2 advisory ignore entries no longer match anything (`quick-xml` already patched in `Cargo.lock`)Open
Difficulty 1/5 Under an hour Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
longbridge/nsh#2758 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
antithesishq/bombadil#473 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
libracoder/kiri#669 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
nowledge-co/hawdb#1881 ·
Maintainers usually reply within 1 day