-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Chat] 전송 실패 메시지 처리 방식 변경 #2938
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -43,7 +43,7 @@ export interface RoomListResultWithPagingInterface | |
export interface RoomMetadata { | ||
name: string | ||
memberCounts: number | ||
faqId?: string | ||
articleId?: string | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 여기 타입이 변경된 히스토리를 알고 싶습니다! There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. #2939 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 앗 cananry 충돌을 방지하기 위해 #2939 내용을 추가하신 것 같네요..! There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. 넵 |
||
} | ||
|
||
export interface RoomInterface { | ||
|
@@ -56,7 +56,7 @@ export interface RoomInterface { | |
members: UserInterface[] | ||
isDirect: boolean | ||
createdAt: string | ||
metadata: RoomMetadata | ||
metadata?: RoomMetadata | ||
} | ||
|
||
export type DisplayTargetAll = 'all' | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
messages와 failedMessages의 렌더링 차이가 없어보여서 [...messages, ...failedMessages]로 합쳐서 렌더링해도 괜찮을 것 같아요!
아니면 ul 태그의 id를 사용하는 경우가 있어 별도로 렌더링을 하는 방법을 택하신 걸까요?👀
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
chat-web은 메시지의 아이디가 숫자로 1씩 올라가게 됩니다. 시간을 기반으로
getTime()
을 한 숫자와 많은 차이가 있겠지만 혹시 id가 겹칠 염려가 있어 두 개를 분리해두었습니다. 추후 메시지 id를 따라 스크롤이 된다거나 하는 등의 기능이 추가될 때를 대비한 바도 있습니다!