Skip to content
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

Phone verification #946

Merged
merged 16 commits into from
Jan 22, 2018
Merged

Phone verification #946

merged 16 commits into from
Jan 22, 2018

Conversation

liamcardenas
Copy link
Contributor

@liamcardenas liamcardenas commented Jan 15, 2018

not quite ready for review yet, still ironing out some things

@ykris45 ykris45 mentioned this pull request Jan 15, 2018
render() {
const { cancelButton, emailErrorMessage, phoneErrorMessage, isPending, fieldType } = this.props;

return fieldType === 'phone' ? (
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a particular reason we use a single component to do two (seemingly) distinct duties, as opposed to UserEmailNew and UserPhoneNew or equivalent?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this was in the spirit of DRY a la our coding maxims.

There is less of a case for userFieldNew to be used for two field types, but userFieldVerify is basically the same for both types. I made userFieldNew to be consistent with that.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't see very much savings here aside from maybe some boilerplate in index.js, and it adds complexity to declaration and handling changes. I'd split these.

)}
</p>
<Form onSubmit={this.handleSubmit.bind(this)}>
<FormRow
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this have to be collected separately as opposed to letting them type a full number? If it is separate field, could it at least be an inline select next to the full number entry?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suppose it could be a select. Twilio wants a separate country code. I tried to make this as fool proof and intuitive as possible. I think the way it is makes a lot of sense (it was based on a discussion in tech-app), but I am completely open to changing it.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@liamcardenas yes, please make the country code a select displayed before the phone number entry.

dispatch(doCloseModal());
dispatch(doNavigate('/rewards'));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it correct to always bump the user to rewards from here?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe so, since the only place you can access this is from the verify identity page.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@kauffj
Copy link
Member

kauffj commented Jan 18, 2018

@liamcardenas Also, I seem to no longer be prompted for my email immediately after the welcome popup.

@liamcardenas
Copy link
Contributor Author

@kauffj oh, for some reason, I thought we were taking that out. Should I add it back in?

@lbry-bot lbry-bot assigned kauffj and unassigned liamcardenas Jan 18, 2018
@liamcardenas liamcardenas assigned liamcardenas and unassigned kauffj Jan 18, 2018
@liamcardenas liamcardenas merged commit f47108c into master Jan 22, 2018
@lyoshenka lyoshenka deleted the twilio branch March 25, 2018 18:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants