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
Issue by thaije Wednesday Feb 26, 2020 at 13:55 GMT Originally opened as matrxs/MATRXS#95
As of now, there is no "type" parameter for Messages.
Furthermore, in the _set_messages functions only the mssg.content is saved, so the agent can never identify different types of messages.
The text was updated successfully, but these errors were encountered:
#230 is planned to be fixed soon, which makes the entire message object available to the agent. In addition, custom message objects that extend the default MATRX message are already supported.
Issue by thaije
Wednesday Feb 26, 2020 at 13:55 GMT
Originally opened as matrxs/MATRXS#95
As of now, there is no "type" parameter for Messages.
Furthermore, in the _set_messages functions only the mssg.content is saved, so the agent can never identify different types of messages.
The text was updated successfully, but these errors were encountered: