5sControl / 5sControl/5s-frontend

Incorrect responses to uploaded files

オープン
#878 コメント 0 件 リアクション 0 件 担当者 1 名 @Ivan0195 が担当を希望しています GitHub で見る
bug
主要言語
TypeScript
スター
3
フォーク
1
PR マージ指標
30日以内にマージされた PR はありません

説明

ОС: macOS
Браузер: Google Chrome

Precondition:
Go to http://192.168.1.120:85/auth/login
Log in to the system
Create a new "Asset Class"
Create "Asset"

Description:
When adding a new "Notes" TaqChat does not respond to the new loaded "Notes". It responds incorrectly or responds that it has no information

Steps:
1. Go to "Templates"
2. Create a new "Template"
3. Link to the desired "Asset Class"
4. Go to the "Connect" tab
5. Select "TaqChat"
6. Send a message with the text "#templateid=6284 The air conditioning is not working well, what could this be related to?"
7. Send a message with the text "The remote control shows error message E101. Do you know what this error means?"
8. Go to the "Templates" tab
9. Load additional "Notes"
10. Return to "TaqChat"
11. Send a message with the text "The remote control shows error message E101. Do you know what this error means?"
12. Send a message with the text "I got error F202. Do you know what this error code is?"

Expected result:
Answers should be constructive and structured. If there is no information to the question, then answer that additional files need to be downloaded or the information is missing.

Actual result:
Responds incorrectly even with compatible files

Request 1
Request 2
Request 3
Request 4
Text 1
Text 2

コントリビューションガイド

コントリビューションガイドを開く

調査の方向性

The issue involves the TaqChat component's handling of uploaded 'Notes' files. Look for the chat interface and file upload logic in the frontend codebase, likely under components related to 'Templates' and 'Connect'. Check how the frontend sends messages and if it properly includes the template ID and references newly uploaded files. The actual result shows incorrect responses, so inspect the API calls and state management for file associations.

索引モデルが issue の本文から書いたものです。

評価

技術スタック
react, typescript
領域
frontend
issue の種類
バグ
難易度
4/5
見積もり時間
3〜5日
活発さ
停滞
明瞭さ
おおむね明確
初心者へのやさしさ
30/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。