-
Notifications
You must be signed in to change notification settings - Fork 1
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
[PAT-1383] Update iOS UI #166
[PAT-1383] Update iOS UI #166
Conversation
6fea956
to
f7000af
Compare
f7000af
to
d7d2b23
Compare
@@ -169,7 +172,10 @@ class DialogBox extends Component<DialogBoxProps> { | |||
const response = await checkRoomStatus(jwt); | |||
const remoteParticipantsStatuses | |||
= getRemoteParticipantsStatuses(response.participant_statuses, participantType); | |||
const jitsiDetails = response ? response.jitsi_details : {}; |
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.
For iOS app we need to explicitly fetch from room status API and set jitsi_details
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.
I remember fetching this in socketConnection.js
. I'm assuming we had to do this again for native? just want to double check
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.
Yes, we have to explicitly do this again for the iOS app to ensure native UI can display the appointment details.
The history is because of a socket.io-client
incompatibility issue there's a WebView for socket connections (with the socketconnection
component within the WebView) in the native iOS app, see L458 of DialogBox.js . Because of this setup the webview and iOS app have have 2 different stores and operates in different environments so we need to fetch room status API again for the iOS app UI.
This was one of the tricky things @ivanjiang5628 and I were discussing with this PR. Hope I got this explanation right
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.
@kaeramirez Thank you!
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.
The changes make sense to me. Just have one minor question.
@@ -169,7 +172,10 @@ class DialogBox extends Component<DialogBoxProps> { | |||
const response = await checkRoomStatus(jwt); | |||
const remoteParticipantsStatuses | |||
= getRemoteParticipantsStatuses(response.participant_statuses, participantType); | |||
const jitsiDetails = response ? response.jitsi_details : {}; |
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.
I remember fetching this in socketConnection.js
. I'm assuming we had to do this again for native? just want to double check
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
b7f3237
to
14b58fb
Compare
We might also want to do a QA for the web app, given the changes to |
Test Plan
Browsers
Pass PR in GitHub / Mark Ready for Release in Jira
|
fc799c9
into
ios-app-release-version-1.5.3-branch
* fix an ios app compilation error that occurred in Metro bundler due to an incorrect import of a web app component in the notifcation/middleware.js file. (#161) * [PAT-1383] Update iOS UI (#166) * Update iOS UI * Fetch room status for iOS * Fix lint issues * fix fix an issue when overwriting the local participant info in Dialogbox component * Fix lint errors * Remove local name check and ensure we always update user's name * prevent re-overwriting the local user information when the waiting room falls back to polling. --------- Co-authored-by: Ivan Jiang <[email protected]> --------- Co-authored-by: kaeramirez <[email protected]>
Description
Updates the iOS UI to fetch Jane appointment details (treatment, treatment duration, start at + end at times and practitioner name) from state
https://jira-jane.atlassian.net/browse/PAT-1383
Release Risk Assessment
Low-med risk since iOS is harder to test
Demo Notes
N/A
QA and Smoke Testing
Expected Behaviour
Other Considerations
Both the iOS version and the web app version of Jitsi
Screenshots
Before
After