Refactor(phone-auth-screen): issue #2812 Updated headers on phone authentication screens to more accurately reflect the type of authentication (creating account versus logging in) #2814
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 some unused code (unused as in it was being overridden) that looked like it was trying to make the header during login to say 'Phone number' as the header. So I followed suit and used that.
For ease of reading the PR, take note of changing the optional property 'type' (in PhoneValidationStackParamList.phoneLoginValidate) to required. There was only 1 instance of this property not being used and that was in 'earns-section.tsx'. It used to pass in undefined and then default to PhoneLoginInitiateType.CreateAccount. Now it's stated there explicitly.