cmd/reticulum-go: use slog for logging #1
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.
Hi,
I've recently started looking into reticulum, as find it easier to learn by experimenting in code than reading. While looking/poking at the code, I noticed that this repo uses it's own custom logging semantics.
Nowadays, the
slog
package is in the golang standard library, much better than the legacylog
, capable of level-filtering and configuring various output-options (json/text etc). This PR switches thecmd/reticulum-go
cmd to use theslog
, but leaves the old logging in the libs. Which becomes a bit odd:I thought I'd check if you're interested in this at all, before I do too much work. If you are, then I can continue and replace it in the remaining code too.
Cheers!