Skip to content
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

remove ChatSubmitType user-newchat #5792

Merged
merged 2 commits into from
Oct 5, 2024
Merged

remove ChatSubmitType user-newchat #5792

merged 2 commits into from
Oct 5, 2024

Conversation

sqs
Copy link
Member

@sqs sqs commented Oct 3, 2024

This controlled whether a chat would reuse the same window or create a new one. Replies and edits reuse the same chat window, but everything else (except for custom commands, optionally) starts a new chat.

The only user-facing behavior change is for custom commands (described below).

The user ChatSubmitType was used in 2 places:

  • For edits in ChatController (not needed, can refactor more simply internally)
  • For custom commands

Since custom commands are being removed and the "reuse existing chat window" of custom commands is not important to preserve even for now, we can simplify the code by removing this mode and submitType throughout.

Test plan

CI & e2e

@sqs sqs marked this pull request as ready for review October 3, 2024 10:26
@sqs sqs requested a review from a team October 3, 2024 10:26
@sqs sqs force-pushed the sqs/chat-submittype branch 2 times, most recently from b352175 to d95e593 Compare October 3, 2024 11:34
The `user` `ChatSubmitType` was used in 2 places:

- For edits in ChatController (an internal use, replaced with `isEdit`)
- For custom commands

Since custom commands are being removed and the "reuse existing chat window" of custom commands is not important to preserve even for now, we can simplify the code by removing this mode and `submitType` throughout.
Copy link
Contributor

@abeatrix abeatrix left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

Q: YK has a PR that I forgot to merge for him before his PTO. This looks like we can still do the behavior Yk is expecting in his PR with this change?
#5698

@sqs
Copy link
Member Author

sqs commented Oct 5, 2024

@abeatrix Thanks! For that PR, it looks like your suggestion is to use user-newchat, which will work because that is now the only behavior.

@sqs sqs merged commit 6798a68 into main Oct 5, 2024
19 checks passed
@sqs sqs deleted the sqs/chat-submittype branch October 5, 2024 06:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants