Fix: Refresh delay and improve performance by using patch strategy to update messages and interactions

[SuZhou-Joe]

Description

[Describe what this change achieves]

Issues Resolved

[List any issues this PR will resolve]

Check List

• New functionality includes testing.
  • All tests pass, including unit test, integration test and doctest
• New functionality has been documented.
  • New functionality has javadoc added
  • New functionality has user manual doc added
• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (a474220) 89.15% compared to head (01a30d1) 93.26%.
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #84      +/-   ##
==========================================
+ Coverage   89.15%   93.26%   +4.10%     
==========================================
  Files          43       46       +3     
  Lines        1033     1218     +185     
  Branches      241      291      +50     
==========================================
+ Hits          921     1136     +215     
+ Misses        111       80      -31     
- Partials        1        2       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[wanglam]

Seems the patch action always follow receive action. Shall we just merge patch action to receive action?

[SuZhou-Joe]

the patch action always follow receive action

For now, yes because for send_message and regenerate action, we append dummy input message and when we do patch, we need to call receive to remove the dummy message. But there are cases that we only call receive action without patch action.

Shall we just merge patch action to receive action

I'd say no because patch action can only do add/update, not able to "remove" a useless message/interaction. Only receive action can do that.

[wanglam]

You're right. I missed the case in loadChat. The loadChat will call receive action without patch.
My original thoughts was to refactor the receive action to accept patch messages and interactions like below code:

    dispatch({
        type: 'receive',
        payload: {
          messages: response.messages,
          interactions: response.interactions,
          patch: {messages, interactions}
        },
      });

We can add an optional patch parameter, and complete patch inside receive action.

[SuZhou-Joe]

I am thinking if that's too much for a single action to do set as well as patch.