-
Notifications
You must be signed in to change notification settings - Fork 3.5k
RECEIVE_RAW_CREATED_MESSAGE
event is never handled
#32
Comments
RECEIVE_RAW_CREATED_MESSAGE
event is never handled
Assuming you're using Browserify, is the Store handling that action actually being |
Please see: https://groups.google.com/forum/#!topic/reactjs/kaQBbTqEj_s Not sure I can implement this without increasing the complexity to the point where it may cause more harm than good. But I will look into fleshing this out more. |
That is, I want to keep the example simple and easy to understand. |
Thanks, please feel free to close this issue. |
FWIW, even if you only implement the happy path acceptance of the "confirmed" message I think it would make this example feel more complete. Right now the complete absence of any handler for this action led me to hunt around to see if I was missing something. A comment about the I could take care of that for you with a PR but I have another related question I posted on the google group where I need some clarification. |
+1 |
Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed. |
Looks like original issue is resolved so closing this out. If there is a specific aspect of the example you feel could be improved (such as adding a comment) a PR would be great. |
Just wondering what happens when
RECEIVE_RAW_CREATED_MESSAGE
was dispatched, currently in the code base it was not handled anywhere.Also, what if
ChatWebAPIUtils.createMessage()
received error from the XHR call to server, what happens next? Should the data already in Stores and Views be rolled back?The text was updated successfully, but these errors were encountered: