-
Notifications
You must be signed in to change notification settings - Fork 525
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
refactor(amazonq): refactor shortAnswer to accommodate API changes #6747
base: master
Are you sure you want to change the base?
Conversation
just testgen related objects extractShortAnswer: use packageInfoList
|
@@ -1175,6 +1175,7 @@ export interface ShortAnswerReference { | |||
} | |||
} | |||
|
|||
// TODO: remove ShortAnswer because it will be deprecated | |||
export interface ShortAnswer { |
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.
Was this ShortAnswer being used any where in the project apart from build and execute in public master branch?
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.
Not being used anywhere else. I will eventually delete this after I do the shortAnswer refactoring for build exec
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.
LGTM.
Can you do E2E testing in these 3 scenarios?
- Success(both ACCEPTED/REJECTED)
- Failed
- Cancelled
Completed testing for success, failed, and cancelled scenarios |
please don't merge yet, thank you!
Problem
Solution
TODO:
feature/x
branches will not be squash-merged at release time.