-
Notifications
You must be signed in to change notification settings - Fork 62
feat(consult-transfer): consult transfer popover improvements #570
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
base: next
Are you sure you want to change the base?
feat(consult-transfer): consult transfer popover improvements #570
Conversation
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
akulakum
left a comment
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.
Please test the End button behavior across Agent, Queue, External Dial Number, and Entry Point Dial Number flows for consult, three-party, and multi-party conference scenarios.
6ba33d9 to
6aa3fa7
Compare
akulakum
left a comment
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. Please fix the minor comment.
| const destAgentType = (task.data.interaction as any).destAgentType; | ||
|
|
||
| return ( | ||
| destAgentType === 'EpDn' || destAgentType === 'EPDN' || destAgentType === 'EntryPoint' || destAgentType === 'EP' |
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.
Please consider using an enum or shared constants for destination agent types to avoid hardcoded strings and improve reusability and maintainability.
Shreyas281299
left a comment
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.
Looks good. But please remove the typecasting that we did in the tests
| variant="small" | ||
| className="tooltip" | ||
| > | ||
| <p>{`Reload ${selectedCategory}`}</p> |
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.
| <p>{`Reload ${selectedCategory}`}</p> | |
| <Text>{`Reload ${selectedCategory}`}</Text> |
| }, | ||
| }, | ||
| }, | ||
| } as ITask; |
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.
Is it possible to avoid typecasting?
| }, | ||
| }, | ||
| }, | ||
| } as ITask; |
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.
Same here
| ...mockTask.data, | ||
| interaction: undefined, | ||
| }, | ||
| } as unknown as ITask; |
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.
Lets try not to do this typecasting this way this test will always pass even if we change anything in the component.


COMPLETES #< CAI-7397 >
This pull request addresses
Enhancements and UI improvements for Consult/Transfer popover behavior.
VIDCAST: https://app.vidcast.io/share/2d81de62-3406-4a15-8ff0-887b8e7e4183
Change Type
The following scenarios were tested
Tested the scenarios in the UI
The GAI Coding Policy And Copyright Annotation Best Practices
Checklist before merging
Make sure to have followed the contributing guidelines before submitting.