[PP-1] Chat history not getting preserved for Deepchat on re-rendering

Created on 10 June 2025, about 1 month ago

Overview

🐛 External AI Chatbot Functionality Active in this the Deep-chat history is not getting preserved on re-rendering the Deep-chat component, which we are intentionally doing to get the values of selected component when creating the components using AI.

key={codeComponentName} causes deep-chat component to re-render.

Proposed resolution

User interface changes

🐛 Bug report
Status

Active

Version

0.0

Component

AI

Created by

🇮🇳India utkarsh_33

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @utkarsh_33
  • 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
  • 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺

    (Based on the title, I thought this was a bug in XB itself. 😇)

  • 🇮🇳India narendraR Jaipur, India
  • 🇺🇸United States tim.plunkett Philadelphia
  • First commit to issue fork.
  • Pipeline finished with Failed
    8 days ago
    #542234
  • 🇳🇱Netherlands balintbrews Amsterdam, NL

    The current MR ensures that the most up-to-date selected component ID is always sent to the controller. However, editing a code component subsequently after creating it still doesn't work, and I'm not sure if that's only because that request never had the right component ID before, and therefore the scenario couldn't be fully tested and implemented. Either way, can I get a review on the current solution and see if anything else is needed here?

  • 🇮🇳India utkarsh_33

    So the current MR fixes the issue mentioned in the IS and the code looks good to me so this can be RTBC'd.
    As far as the issue mentioned by @balintbrews in #9 🐛 [PP-1] Chat history not getting preserved for Deepchat on re-rendering Active is something that i can see in the network tab once the component is created but not when i try to edit the component using the code editor or using the AI bot.
    It might be because of following code:-

    const component = message.component_structure;
        await createCodeComponent(component).unwrap();
        navigate(`/code-editor/component/${component.machineName}`);

    Upon quickly debugging i found that component.status is false, but didn't investigate much in detail as this can be fixed as a separate issue.
    @balintbrews if you think that it's not a hard blocker for this issue then i can open another issue for the point you mentioned in #9 and we can keep this issue moving forward.

  • Pipeline finished with Failed
    7 days ago
    Total: 939s
    #542813
  • Pipeline finished with Skipped
    7 days ago
    #542839
  • Pipeline finished with Skipped
    7 days ago
    #542840
    • balintbrews committed d4e377b2 on 0.x
      Issue #3529328 by balintbrews, utkarsh_33: Selected component value not...
  • 🇳🇱Netherlands balintbrews Amsterdam, NL

    We looked into this together with @utkarsh_33. #10 is all expected, so that's not something to be concerned about. Utkarsh is not able to reproduce what I'm seeing, while I consistently can. Granted, we're using different AI providers, which shouldn't be a problem, but maybe that's where things go differently. Either way, I'm opening a new issue to describe things in detail.

    We agreed that this issue is good to land.

Production build 0.71.5 2024