3.1.0
Changes since 0.2.2:
Breaking Changes
-
BREAKING CHANGE: removed NetworkTables.createInstance*()
- Please use NetworkTables.getInstanceByTeam() and NetworkTables.getInstanceByURI()
-
BREAKING CHANGE: removed NetworkTableTypeInfos
- Fixed typo: now called
NetworkTablesTypeInfos
(NetworkTables plural! With S!)
- Fixed typo: now called
-
BREAKING CHANGE: Remove immediateNotify from subscribe
- This complicated prefix topics and was not a very valuable feature
- Workaround: you can manually call the subscription's callback yourself after subscribing
-
BREAKING CHANGE: Drop active support for v4.0
- The API now recommends NT v4.1 to function
-
BRAKING CHANGE: publish and setProperties are now asynchronous
- Please await these calls to know when the changes take effect
- After awaiting publish, it is safe to set new values to the topic
- Please await these calls to know when the changes take effect
Changes
-
Fix 2025 Robot issues
- Fixes publisher and subscriber ID generations to start counting at 0. Avoids integer overflows.
- Remove RTT websocket that is unnecessary since the client can respond to PING and PONG messages
-
Fix timeout for publishing pre-connection to wait for robot connection
-
Add prefix topic support
- You can now subscribe to multiple topics with a single subscription
- This is done by creating a topic with a prefix, and then subscribing to that topic
- For example, if you have topics
/MyTable/Accelerometer/X
,/MyTable/Accelerometer/Y
, and/MyTable/Accelerometer/Z
, you can create a prefix topic/MyTable/Accelerometer/
and subscribe to that to get notifications for all three subtopics
-
Add support for v4.1
- No support added yet for cached messages
-
Updated dependencies
Full Changelog: 0.2.2...3.1.0