Functions like MapMsg can't be compared directly so we rely on a hard-coded ScalarAttributeComparison.
MapMsg was set to Identical which will force Fabulous to still use the initial MapMsg, even in case of reuse with a different MapMsg.
We simply need to set it to Different to fix that.
Functions like MapMsg can't be compared directly so we rely on a hard-coded ScalarAttributeComparison. MapMsg was set to
Identical
which will force Fabulous to still use the initial MapMsg, even in case of reuse with a different MapMsg.We simply need to set it to
Different
to fix that.