typelevel / typelevel/natchez

Entry point log-odin doesn't provide the ability to overwrite the json formatter

Open
#1,228 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Scala
Stars
340
Forks
76
Avg merge
1d 6h
Merged PRs (30d)
13

Description

In the Log.entryPoint there is a convenient way to specify a json formatter.
It would be nice to have it also in the log-odin version of it.

Contributor guide

Open the contributing guide

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.

Research direction

Start by comparing the existing Log.entryPoint JSON formatter option with the log-odin entry point. Trace how each entry point accepts formatter configuration, then make the log-odin API offer the same override capability. Done means callers can provide a custom JSON formatter through log-odin as they can through Log.entryPoint.

Written by the indexing model from the issue text.

Assessment

Tech stack
scala
Domain
observability-sre
Issue type
Feature
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.