You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@yrh012 found out that if you add an input of a certain state representation type (so EncodedType), and connect it to a topic that is also publishing an encoded state but of different state representation type, the attribute will be overridden with the received message. If we want to be consistent with C++, we should probably attempt a cast on the received message such that the attribute type of the subscribing component doesn't change.
Classic Python. It's true that from the users perspective, the type of the class attribute should not change if a valid input is received and decoded. For the best way to implement it, I am not sure, but it seems like a reasonable backlog issue to address whenever a contributor has some time.
modulo/source/modulo_components/modulo_components/component_interface.py
Line 429 in 59b4b6e
@yrh012 found out that if you add an input of a certain state representation type (so
EncodedType
), and connect it to a topic that is also publishing an encoded state but of different state representation type, the attribute will be overridden with the received message. If we want to be consistent with C++, we should probably attempt a cast on the received message such that the attribute type of the subscribing component doesn't change.Opinions? @eeberhard @bpapaspyros
The text was updated successfully, but these errors were encountered: