Wondering if it would be feasible to add the ability to bind the message handler message type to a property.
As in, you want to be able to dynamically switch which message "type" you're listening for?
That's...pretty unlikely to happen, due to how this all works under the hood. Or did I misunderstand your request?
I mean, I wouldn't be dynamically changing the type in runtime. All the session props are static and won't change (unless changing in the designer).
The reason I use the custom session props for all the other message handler properties is because I don't want to fat-finger any of the strings or get the wrong capitalization.
Alternate solution would be a message handler management utility of some sort.
Well, a binding is a binding is a binding. We don't have any concept of "compile time" binding evaluation, so even though your use case wouldn't require runtime evaluation, the machinery would have to support it. Which circles back to "probably not going to happen".
I can see the appeal of eliminating repeated string references though, for sure. It's an interesting idea to kick around. There may be something we can do within the designer to make things a bit "smarter", like an autocomplete for defined message handlers/broadcast types, perhaps.
4 Likes