Switch to using POST messages.json for single message sends about rapidpro HOT 4 CLOSED

We're not trying to get smart about broadcasts sent to one contact - sending a broadcast should always create a broadcast. Flow editor never calls these endpoints because it never directly sends anything.

Just need to update chat widget on new UI contact read page and on ticket read page (same in old and new UI).

from rapidpro.

@rowanseymour ok i think this one is mostly clear (re: chatbox on the contact read and ticket pages), but do we expect this update to be needed across both the floweditor and temba-components repos? i think there are some scenarios where something in a flow could result in a "single messsage send" ex. if a flow contains the send msg node and only specifies one contact? also, i think in the old ui there is a "send message" button which brings up a modal specifying just the one contact?... so yeah, just want to confirm what's included in the scope of this work...

and then below are just a few quick questions to sanity check any discrepancies with the work across repos, old vs. new ui, and to also snag any relevant navigation steps/links to more quickly zero in on where the change needs to happen:

• repo - changes needed in only floweditor vs only temba-components vs both?
• ui - changes needed for only new ui vs. partial old and new ui vs both old and new ui?
  • only new ui => no affect to old ui
  • partial old and new ui => needs to maintain status quo display/behavior of old ui
  • both old and new ui => will result in a change of display/behavior in old ui
• navigation - link/steps to where change is needed in old and new ui?

thanks for bearing with on the above!

from rapidpro.

One issue with this is that we probably want a created_by on Msg before making this change. This is pretty important in the ticketing view to see which agent sent which message. Today, this uses Broadcast.created_by

from rapidpro.

@ericnewcomer good point - just made #4379 and nyaruka/mailroom#44

from rapidpro.