Warning me when there's warnings
Nobody has claimed this yet.
- Dominant language
- Racket
- Stars
- 516
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
Description
Say I run this program in DrRacket:
#lang racket
(log-error "Whizzbang not frobnicated, continuing unsnoozled")
By default, nothing happens at all. If I remember to go to View > Show Log I can see the message and change message filtering, but how am I supposed to know when to do that? Should I do that every time? How many Typed Racket dead code warnings have I missed over the years?
I'd like it if DrRacket had some small status message or icon somewhere that meant "Hey you! There's warnings, click here!". Maybe some yellow-ish text printed right after the "Language: racket, with debugging; memory limit: 2048 MB" line in the interactions window since that's where my eye goes anyway when I run code.
I have no idea how this should work with log messages at higher phases or during background expansion.
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
Reproduce the example in DrRacket, then inspect View > Show Log and the interactions window around the “Language: racket...” line. Clarify how warnings from log messages and higher phases or background expansion should be surfaced; done should include a discoverable indication when warnings exist and a way to inspect them.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100