Closed
Bug 1080387
Opened 10 years ago
Closed 9 years ago
The AcceptCallButton component should manage its own logic, not via IncomingConversationView
Categories
(Hello (Loop) :: Client, defect, P5)
Hello (Loop)
Client
Tracking
(Not tracked)
RESOLVED
WONTFIX
backlog | tech-debt |
People
(Reporter: standard8, Unassigned)
References
Details
(Whiteboard: [tech-debt])
The AcceptCallButton is currently not managing its own logic, but is being passed a function from the IncomingConversationView (IncomingConversationView#_answerModeProps). This makes it hard to unit test that items are working correctly, as the logic, tooltips and classes are spread across multiple components. We should move the logic into AcceptCallButton, with the only props needed being: - The default type of call (if video or not) - A function to handle the action if the button is clicked. This is split out from bug 1079128 where we discussed doing a unit test, but found it too difficult.
Updated•10 years ago
|
backlog: --- → Fx36+
Updated•10 years ago
|
backlog: Fx36+ → Fx37+
Updated•9 years ago
|
backlog: Fx37+ → Fx38?
Reporter | ||
Updated•9 years ago
|
backlog: Fx38? → tech-debt
Priority: -- → P5
Reporter | ||
Comment 1•9 years ago
|
||
We are currently reworking the Loop "user journey" (bug 1209713) and as part of this direct calls and contacts are being removed. Therefore closing direct call related bugs as wontfix. Tracking id: directcallclosing
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•