fix: improve BlueBubbles log commands#7
Merged
Conversation
0eed305 to
3691d1a
Compare
Owner
Author
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.
Summary
bluebubbles server logsdefault to the live BlueBubbles server logs APIbluebubbles server logs --source localfor configured or CLI-owned local log files--source localis usedWhy
bluebubbles server logspreviously failed when the CLI had not launched the app and nologPathwas configured, even though the server API could return live logs. The command now follows the server-resource/API shape by default.Validation
bun test src/index.test.ts src/lib/*.test.tsbun run checkbun run buildbluebubbles server logs --count 5bluebubbles logs --count 5returns unknown commandLinks