Compare commits

..

4 Commits

Author SHA1 Message Date
9dd1d0dc53
provide better feedback when we have exhausted all config_pb2 options
Signed-off-by: Brian S. Stephan <bss@incorporeal.org>
2024-12-17 13:44:30 -06:00
62c7fad02c
properly test protobuf structure packaging options
this should all be tested now:
1. invoking against precompiled _pb2.py files provided by user
2. invoking against .proto files provided by user which must be compiled
3. invoking with a special option to use shipped (by us) .proto files
   which must be compiled
4. erroring because none of the above occurred

this took some reorganization, but this should finally give me stability
in using this in GP2040-CE's build process

Signed-off-by: Brian S. Stephan <bss@incorporeal.org>
2024-12-17 13:30:25 -06:00
c4e253b4e0
tweak the debugging output of getting protobuf modules
Signed-off-by: Brian S. Stephan <bss@incorporeal.org>
2024-12-17 12:18:34 -06:00
1801f43d38
version bumps, which necessitated a small version update
for some reason the GUI pilot server for testing doesn't go to the end
of the input field for edits, so the things that backspaced over old
values need an extra 'end' keypress now. I didn't look into why this is,
because it's fine in the actual GUI regardless

Signed-off-by: Brian S. Stephan <bss@incorporeal.org>
2024-12-17 08:22:03 -06:00

View File

@ -3,19 +3,6 @@
Included is a summary of changes to the project. For full details, especially on behind-the-scenes code changes and
development tools, see the commit history.
## v0.11.0
### Improvements
* The usage of provided GP2040-CE config Protobuf files must be explicitly specified via the `-S` flag. This is in order
to not accidentally fall back to them and be confused by the results. The net effect is that in most situations, users
will have to provide either `-P PATH` or `-S`.
* The testing of the above fallbacks covers the options far better than before now.
### Miscellaneous
* Version bumps, which brought about a couple updates to the tests.
## v0.10.0
### Features