-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
update sign in page structure #36803
Merged
srikarparsi
merged 6 commits into
Expensify:main
from
suneox:36515-update-sign-in-page-structure
Feb 24, 2024
Merged
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
d37d2ad
update SignInPage structure
suneox 4deab03
fix sign page typecheck
suneox 76b746c
Merge remote-tracking branch 'upstream/main' into 36515-update-sign-i…
suneox a4fab45
fix prettier
suneox e469805
Merge remote-tracking branch 'upstream/main' into 36515-update-sign-i…
suneox 80863fe
fix prettier
suneox 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 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.
Thinking about this, I can't see a good reason to introduce
shouldEnableMaxHeight
as a prop asSignInPage
isn't being used from anywhere else, so we could just set it to false here. Or am I missing something? 😄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.
@suneox Friendly bump on this question 🙇
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.
Due to SignInPage use default at Router, and re-use at SignInModal so we should set default for a use case Router render
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.
Did you test for that case? I think it would also want the same fix applied, no?
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 have test and also provide screenshot in Screenshots/Videos
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 meant have you tested for the case where the
SignInModal
is used inRouter
? I don't think I agree that it should have a different value forshouldEnableMaxHeight
.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 i have tested both cases using
SignInModal
atApp/src/libs/Navigation/AppNavigator/PublicScreens.tsx
Lines 21 to 25 in 52b6d70
and
App/src/pages/signin/SignInModal.tsx
Lines 22 to 30 in 52b6d70
@jjcoffee
We have a different value for
SignInPage
due to atSignInModal
has a HeaderWithBackButton and already set shouldEnableMaxHeightso when
SignInModal
reuses aSignInPage
as a component we should disableshouldEnableMaxHeight
onSignInPage
to avoid a double scroll bar (due toshouldEnableMaxHeight
will get the screen height + HeaderWithBackButton).