Skip to content

Conversation

@ctlai95
Copy link
Contributor

@ctlai95 ctlai95 commented Apr 5, 2025

Problem

History logic cleanup

Solution

  • History does not need to be in triggerPayload
  • ChatHistory does not need tools
  • We don't need to create and maintain a separate newUserMessage object

  • Treat all work as PUBLIC. Private feature/x branches will not be squash-merged at release time.
  • Your code changes must meet the guidelines in CONTRIBUTING.md.
  • License: I confirm that my contribution is made under the terms of the Apache 2.0 license.

@github-actions
Copy link

github-actions bot commented Apr 5, 2025

  • This pull request modifies code in src/* but no tests were added/updated.
    • Confirm whether tests should be added or ensure the PR description explains why tests are not required.

@ctlai95 ctlai95 marked this pull request as ready for review April 5, 2025 00:29
@ctlai95 ctlai95 requested a review from a team as a code owner April 5, 2025 00:29
@zixlin7 zixlin7 merged commit a4627c7 into aws:feature/agentic-chat Apr 5, 2025
21 of 22 checks passed
laileni-aws added a commit to laileni-aws/aws-toolkit-vscode that referenced this pull request Apr 5, 2025
* pair programming mode

* pairProgrammingModeOn boolean

* use session in chatHistory

* revert chatHistory

* client side toolName validation

* refactor(chat): simplify history logic (aws#6946)

## Problem
History logic cleanup

## Solution
- History does not need to be in triggerPayload
- ChatHistory does not need tools
- We don't need to create and maintain a separate newUserMessage object

---

- Treat all work as PUBLIC. Private `feature/x` branches will not be
squash-merged at release time.
- Your code changes must meet the guidelines in
[CONTRIBUTING.md](https://github.com/aws/aws-toolkit-vscode/blob/master/CONTRIBUTING.md#guidelines).
- License: I confirm that my contribution is made under the terms of the
Apache 2.0 license.

---------

Co-authored-by: Jacob Chung <[email protected]>
Co-authored-by: Tai Lai <[email protected]>
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.

4 participants