luckyframework / luckyframework/dexter

Evaluate the future of this library

Open
#38 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Crystal
Stars
21
Forks
4
PR merge metrics
No merged PRs in 30d

Description

My understanding of history is that this library was made in a time where Crystal's `Log` class was not very robust and this library added functionality that was missing. (From what I've heard) The `Log` class is now better so we need to figure out what Dexter should look like going into the future and if there is even a place for it.

Should Dexter just be a library of formatters? [Lucky has some formatters](https://github.com/luckyframework/lucky/blob/master/src/lucky/pretty_log_formatter.cr) so should they be moved over or is it even worth it?

Contributor guide

No contributing guide indexed for this repository

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 Dexter's current purpose with Crystal's Log class and the Lucky formatter implementation linked in the issue. The issue is complete only after the project's future scope is decided, including whether Dexter remains a library, focuses on formatters, or is retired or moved.

Written by the indexing model from the issue text.

Assessment

Tech stack
crystal
Domain
observability-sre
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.