Repository navigation
feat(app): Logs page with recent events and a level filter (#253) - #327
Merged
Merged
Conversation
Contributor
|
/mira pause |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
Member
Author
|
No Mira review (auto-paused). All checks green; merging. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Part of #253 (Logs slice).
Adds
/logsto the running app:%LOCALAPPDATA%\nowplaying\logs\nowplaying.log(last 64 KB, up to 200 events), newest first, refreshing every 3 sPrivacy: the log already holds only time, level, component, status and a short code.
log-tail.jschecks each line against that shape again and drops anything else, so a hand-edited log can't put a server address or token on the page./api/logsis GET/HEAD only and refuses cross-site requests; a read error returnslog_unreadablewithout the path.Levels use the existing classes: warning and error are orange shades, never red/green. The troubleshooting doc mentions the page.