[wip] More precise type hints for rosbag2_py
#1463
Draft
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.
VERY WIP
Meant to address #1459
For now, the only improved type hint is for
SequentialReader.read_next
and the type stubs need to be generated manually.This branch has many other changes I made to make development easier for me. I'm guessing
rosbag2
doesn't actually want them, in which case they'd be removed before this PR is un-drafted.These changes are:
.devcontainer
andDockerfile
. Currently these mention my username. If the devcontainer is kept, I'd remove that username-specific bit. These were made following this guide for getting ROS2 in a devcontainer.rosbag2_py
now useunittest.TestCase
, so that I can run them from the VSCode test panel, without running the entirecolcon test
..github
workflows (you definitely don't want this change)