lambdaisland / lambdaisland/kaocha
Reconsider notification levels (urgency)
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 860
- Forks
- 81
- PR merge metrics
- No merged PRs in 30d
Description
Currently the notifier plugin logs failing tests with an "urgency" of "critical", this causes the notifications to become persistent on certain systems (at least KDE, possibly also gnome).
I would like to see two changes
a) a breaking change moving from urgencies "normal" and "critical" to "low" and "normal"
b) making the level configurable
:kaocha.plugin.notifier/urgency :normal
With possible values
:auto, the default, use low/normal depending on result:low/:normal/:critical: use fixed value
Note that this currently only impacts linux.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating the notifier plugin and the code that assigns urgency to failing and passing test notifications. Check how plugin configuration is read, then verify the proposed auto, low, normal, and critical values against Linux notification behavior; done means both urgency changes and configurability are covered.
Written by the indexing model from the issue text.
Assessment
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100