-
Notifications
You must be signed in to change notification settings - Fork 737
fix(dev): Allow user access history diff generated along iterations #5756
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
Conversation
|
This pull request implements a feature or fix, so it must include a changelog entry. See CONTRIBUTING.md#changelog for instructions. |
| new AppToWebViewMessageDispatcher(new MessagePublisher<any>(new vscode.EventEmitter<any>())) | ||
| ), | ||
| telemetry: new TelemetryHelper(), | ||
| uploadHistory: {}, |
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.
nit: Consider adding a test where uploadHistory is populated and show we can access an element from it
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.
Sorry, used the wrong account here.
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.
Oh, I thought was somekind of automatic messaging. Thanks, yea, due the timeline I would say we can add those testing scenarios as a follow up PR
| new AppToWebViewMessageDispatcher(new MessagePublisher<any>(new vscode.EventEmitter<any>())) | ||
| ), | ||
| telemetry: new TelemetryHelper(), | ||
| uploadHistory: {}, |
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.
Sorry, used the wrong account here.
packages/amazonq/.changes/next-release/Bug Fix-dd58d9cb-4fb4-4cb3-a9a2-dc5c5462e529.json
Outdated
Show resolved
Hide resolved
…cb3-a9a2-dc5c5462e529.json Co-authored-by: Justin M. Keyes <[email protected]>
Problem
We currently only support accessing the last code generated (by the Tree view). If you try open the diff view in past history, will thrown an error. This happens because when we click on past history Tree we actually send a "newer" uploadId and didn't keep track of all the past ones.
Solution
Cache those uploadIds based on codeGenerationId which can be easily accessible while clicking in past views.
License: I confirm that my contribution is made under the terms of the Apache 2.0 license.