Repository navigation
Conversation
`DECODED_FIRMWARE` becomes `FIRMWARE_1_RANGE`, unchanged at (1300, 1999): the 1.x line's range, so a 2.x range can sit beside it. No bytes sent and no results change. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
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.
The Problem
DECODED_FIRMWAREholds the 1.x firmware whose replies the driver reads. Two firmware lines now need such a range: the 1.x line, which #1606 widens to 1.20, and 2.x, whose replies are laid out differently. A name that says which line it belongs to lets the second range sit beside it.PR Content/Solution
DECODED_FIRMWARE→FIRMWARE_1_RANGE, unchanged at(1300, 1999); its comment and the docstrings that name it follow.🤖 Generated with Claude Code