feat: packet inspector detail for non-raw packets - #25
Merged
Conversation
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.
What changed
PacketDetail.vueshows, per selected row:payload_json(the raw library event payload).attributes_jsonwhen present.Packets.vuefetches the full row viaGET /api/packets/{id}for non-raw rows (the list view omits the JSON blobs); raw packets keep the existing hex breakout.Why
The inspector previously only worked for RX_LOG raw frames; every other packet type showed a dead-end message even though the data (
payload_json/attributes_json+ envelope columns) was already stored. This surfaces what the bot is doing/seeing for each event.Breaking changes
None. Frontend-only; no API or schema changes. Rebuilt
webapi/static/assets included.