feat: change IRequest answer type

[kilativ-dotcom]

Important

Change IRequest answer type to TextItem[] and update components to handle this type.

• Behavior:
  • Change answer type in IRequest from any to TextItem[] in requestDialogHistorySlice.ts.
  • Update AskAnswer.tsx to store answers as TextItem[] and dispatch them correctly.
  • Modify fetchAnswerByQuery to create TextItem[] for both found and not found answers.
• Components:
  • Enable AnswerText component in AskElement.tsx to render TextItem[].
  • Uncomment AnswerText usage in AskElement.tsx.
• Misc:
  • Remove commented-out code for translation in AskAnswer.tsx.

^{This description was created by for 37abd9a. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Caution

Changes requested ❌

Reviewed everything up to 37abd9a in 1 minute and 43 seconds. Click for details.

• Reviewed 110 lines of code in 4 files
• Skipped 0 files when reviewing.
• Skipped posting 1 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. src/components/AskAnswer/AskElement/AskElement.tsx:9

• Draft comment:
  Avoid using 'any' for the answer prop; update the IProps interface to use the TextItem[] type for better type safety.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_1TYSLLu8qD2yc97e

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Use an inline array literal for readability. Instead of creating an empty array and pushing, consider: const items = [{ type: 'normal', content: answer }].

[ellipsis-dev]

Remove the commented-out translation code if it is no longer needed to keep the code clean.