json-log-viewer
json-log-viewer copied to clipboard
Interactive viewer for JSON logs.
Support search over all fields. Create [a new state](https://github.com/hedhyw/json-log-viewer/tree/main/internal/app) in which: - up -> go to the previously found line; - down -> go to the next found line; -...
The place is: https://github.com/hedhyw/json-log-viewer/blob/bbae13d2754cb885c2f0f986aa4dda2a9a5eb9ec/go.mod#L5 More details: https://github.com/antonmedv/fx/issues/256
The place is: https://github.com/hedhyw/json-log-viewer/blob/3a474972288146cef2bac25eb50b0e6b4c80a4bf/go.mod#L7 After merging: https://github.com/charmbracelet/bubbles/pull/397
Support after-refreshing of logs. It should be [configurable](https://github.com/hedhyw/json-log-viewer/blob/main/internal/pkg/config/config.go). Default: every 10s. Keep the cursor on the same position.
Pino (the popular node logger) user number for log levels: https://github.com/pinojs/pino/blob/main/docs/api.md#loggerlevels-object A quick solution for this single case would be to add the numbers as aliases for the log levels....
Bumps [github.com/charmbracelet/lipgloss](https://github.com/charmbracelet/lipgloss) from 0.11.0 to 0.12.1. Release notes Sourced from github.com/charmbracelet/lipgloss's releases. v0.12.1 This release fixes a regression with regard to border calculations introduced in Lip Gloss v0.11.1. Thoughts? Questions?...
Bumps [goreleaser/goreleaser-action](https://github.com/goreleaser/goreleaser-action) from 5 to 6. Release notes Sourced from goreleaser/goreleaser-action's releases. v6.0.0 [!WARNING] This is a breaking change! Follow the instructions here to upgrade! What's Changed feat!: use "~>...
Bumps [github.com/charmbracelet/bubbletea](https://github.com/charmbracelet/bubbletea) from 0.25.0 to 0.26.6. Release notes Sourced from github.com/charmbracelet/bubbletea's releases. v0.26.6 Changelog Bug fixes 60a57eaf1f7f71e6678af1607581fad369cd6e88: fix: nil deref on release terminal (@aymanbagabas) Thoughts? Questions? We love hearing from...
It appears to take much longer to load the log data but I found out that just a "rendering" issue. If I just open a log file and do nothing...