-
Notifications
You must be signed in to change notification settings - Fork 305
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
[P2PS] / Ameerul / P2PS-4532 PA client gets logout when login #17699
base: master
Are you sure you want to change the base?
[P2PS] / Ameerul / P2PS-4532 PA client gets logout when login #17699
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Pull Request Test Coverage Report for Build 12116320764Warning: This coverage report may be inaccurate.This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.
Details
💛 - Coveralls |
A production App ID was automatically generated for this PR. (log)
Click here to copy & paste above information.
|
🚨 Lighthouse report for the changes in this PR:
Lighthouse ran with https://deriv-app-git-fork-ameerul-deriv-p2ps-4532-pa-client-get-d8e664.binary.sx/ |
@@ -1635,7 +1635,7 @@ export default class ClientStore extends BaseStore { | |||
if (this.is_logged_in) { | |||
this.getWalletMigrationState(); | |||
|
|||
await WS.mt5LoginList().then(this.responseMt5LoginList); | |||
await WS.authorized.mt5LoginList().then(this.responseMt5LoginList); |
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.
will this have any impact on the user? From what yashim has explained to me, this will slow the call a little since it will check for auth first before calling mt5_login_list, but will this impact any other major flows?
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.
we are already checking this.is_logged_in
then why need authorized
again?
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.
because for certain PA accounts, (idk why this happens) it will call this specific mt5_login_list
endpoint before we authorize during login. Currently when we login, one websocket is created, and then a second is created, and this mt5_login_list
gets called in the second websocket, before authorize. So we need to use WS.authorized
to make sure it waits for authorized call before calling mt5_login_list
Changes:
Please provide a summary of the change.
Screenshots:
Please provide some screenshots of the change.