[go] Allow user-defined Logger

Open
#531 2 comments 0 reactions 0 assignees View on GitHub

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

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from bytecodealliance/wrpc

All issues in bytecodealliance/wrpc

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.