-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Remove unnecessary calls to OpenPrivatePersonalDetailsPage #37047
Merged
Merged
Changes from 21 commits
Commits
Show all changes
25 commits
Select commit
Hold shift + click to select a range
627bdf2
Remove unnecssary calls to OpenPrivatePersonalDetailsPage
grgia e5b5536
remaining uses
grgia ed012d5
prettier
grgia 8410d34
fix LegalNamePage loading
grgia e33dc85
fix direct link loading for AddressPage
grgia 3d31a5e
Loading pages
grgia 26d1f57
prettier
grgia 5b33277
remove unused function
grgia d968e0b
add default props to profilepage
grgia bbf8366
Merge branch 'main' into georgia-private-personal-details
grgia dd90ad3
use hook
grgia b42b0b8
Merge branch 'main' into georgia-private-personal-details
grgia 8130664
Merge branch 'main' into georgia-private-personal-details
grgia 96a20fa
remove weird merge file creation
grgia cc9b06a
Clean up
grgia c79637c
leave TS type
grgia 67595c7
Merge branch 'main' into georgia-private-personal-details
grgia 1bd4b0a
remove hook and calls to to get private personal details
grgia d6f6d2f
lint
grgia 970229a
fix lint
grgia b3bc589
TS error
grgia b9b2a43
Merge branch 'main' into georgia-private-personal-details
grgia f8f785e
Merge branch 'main' into georgia-private-personal-details
grgia f09f94b
Merge branch 'main' into georgia-private-personal-details
grgia bfd8fb9
remove openPersonalDetails, update test to call openPublicProfilePage…
grgia File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
@s77rt Im wondering about leaving this hook/function instead of deleting it for later if we need to load confidential data for some reason. What do you think? Or should we just add this back when we later need it
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 should just add it back when needed. It's always best to avoid unnecessary code hanging in the code base. FWIW I don't think we would ever need this hook again since we will always have the private data on OpenApp
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.
Although, I realize that currently logged in users wont have the data unless they log out and back in / reconnect
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.
Oh right! This is a breaking change for logged users. But it's a temporarily issue. Can we maybe send pusher events to all users to get their private data?
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.
@grgia Was there any discussion regarding this issue? or whether it's a blocker?
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'm not sure if it makes sense to keep the call for one page only, it may be better to do nothing and close the PR. However I'm inclined to remove the redundancy. I just realized something, how can a user upgrade the app and not call
OpenApp
?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.
Yeah that's a good point. @marcaaron mind if I ask for your expertise here?
Essentially, we've added the privatePersonalDetails to openApp, so there's no need to send them on these pages. However, we're concerned that this is a breaking change for users until openApp is called when they log in / out. Is this something I need to worry about?
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.
@grgia can you help me understand the consequences of showing the stale data to the affected users?
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.
@marcaaron we didn't use to store these private personal details in ONYX, now we do via Open App. So any users who havent logged in yet or called OpenApp in awhile wouldnt have the data in ONYX to access.
So the question is, do we keep a call to the API 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.
Hmm I don't feel too passionate. It feels like we can remove it? Unless something major will break I would treat it as a minor bug affecting older app versions. We are going to force upgrade users to use a new version of the app eventually which should trigger an OpenApp call (at least in the case of native apps).