typelevel/skunk

Add option to turn off emojis in exceptions

Open

#1,138 创建于 2024年10月23日

在 GitHub 查看
 (3 评论) (4 反应) (0 负责人)Scala (1,656 star) (172 fork)batch import
good first issue

描述

The flood of 🔥 emojis looks cool and definitely draws attention when you hit an issue in local development, but it's not well supported in all CI systems, and certainly not in all logging systems. There should be a way to tweak this behavior, perhaps even with sane defaults such as disabling the fires when CI=1 or based on some terminal variables.

贡献者指南

技术栈
scalapostgresql
领域
backenddatabase
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
2
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-3 hours
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
mostly clear
前置要求
Scala basicsFamiliarity with Skunk's error handling
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
75
研究方向
Start by examining the exception formatting code in the Skunk source, likely in the error or exception handling module. Look for where emojis are injected into error messages. The issue suggests adding a configuration option, possibly via an environment variable like CI=1 to disable emojis automatically. Consider modeling the solution after existing configuration patterns in the library. Review the issue comments for any additional suggestions from maintainers.