Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add `schemaName` field to MessageEvent
See original GitHub issueWhen a panel receives message events for subscribed topics, it might need to take different code paths depending on the type of the received message.
For example - the Image panel needs to know if the message it received should be processed as a ROS ImageMarkerArray or a foxglove.ImageAnnotations message. The schemaName determines which fields are expected and their semantics.
The existing array of message events does not convey this information as only ROS message datatypes were previously supported.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
We use
schemaNamein both mcap and ws-protocol, so I vote we start using that term consistently everywhere, and clean up places in our UI + docs (and preferably our codebase too) where other terms likedatatypeare used indiscriminately.I have no memory of making this comment but apparently I am internally consistent over 6 months.