Skip to content
This repository has been archived by the owner on Jan 12, 2019. It is now read-only.

Option to add "Cardholder Name" field to manual entry form #39

Merged
merged 1 commit into from
Dec 2, 2015

Conversation

dsn5ft
Copy link
Contributor

@dsn5ft dsn5ft commented Nov 13, 2015

All tests passed on a Moto X 2nd Gen device running Android 5.1

Localized strings from Google translate, waiting on official list from PayPal translation team

@dsn5ft
Copy link
Contributor Author

dsn5ft commented Nov 13, 2015

Field Empty Example:

screenshot-2015-11-12_20 03 28 777

Field With Text Example:

screenshot-2015-11-12_20 03 29 686

@dsn5ft
Copy link
Contributor Author

dsn5ft commented Nov 13, 2015

@braebot I got the localized strings using google translate like you suggested, let me know what the next step is whenever you have a chance

@@ -48,6 +49,7 @@
* PayPal REST Apis only handle max 20 chars postal code, so we'll do the same here.
*/
private static final int MAX_POSTAL_CODE_LENGTH = 20;
private static final int MAX_NAME_ON_CARD_LENGTH = 50;
Copy link
Member

Choose a reason for hiding this comment

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

Why is this 50? According to Braintree docs, 175 is the max, while Visa/Mastercard are issuing new cards with 22 char limit. Would be good to have a reason for the length 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 couldn't find a standard max value but I can update it to 175 if that's the braintree max

Copy link
Member

Choose a reason for hiding this comment

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

Yes please, let's do that, unless another limiting factor requires it to go lower.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will do

@braebot
Copy link
Member

braebot commented Nov 13, 2015

Overall code looks good. However, I don't like the "Name on Card" string or related extra/variable names. According to the git history, it was originally Cardholder name, but was modified to Name on Card, without a reason given. What were your thoughts there?

@dsn5ft
Copy link
Contributor Author

dsn5ft commented Nov 13, 2015

So we actually had an internal discussion about "Name on Card" vs "Cardholder Name" and our product team landed on "Name on Card", however if you think "Cardholder Name" is more inline with Braintree terminology then we can definitely switch it back to that (I personally did like "Cardholder Name" more).

@dsn5ft
Copy link
Contributor Author

dsn5ft commented Nov 13, 2015

@braebot I have a branch with the rename back to "Cardholder Name". do you think that's the way to go?

@braebot
Copy link
Member

braebot commented Nov 13, 2015

Yes, but I think at least one of the other @card-io/developers should chime in, since whatever name we pick will go in iOS too.

@dsn5ft dsn5ft changed the title Option to add "Name on Card" field to manual entry form Option to add "Cardholder Name" field to manual entry form Nov 14, 2015
@dsn5ft
Copy link
Contributor Author

dsn5ft commented Nov 18, 2015

@braebot Now that there is an iOS equivalent pull request for this feature (card-io/card.io-iOS-source#45), is there anyway we can get a final confirmation on the Cardholder Name string so we can update our pull requests if needed and get them merged in once they are reviewed and certified?

@braebot
Copy link
Member

braebot commented Nov 18, 2015

@dsn5ft, thanks for iOS PR! I'll bug the other contributors to chime in so we can send this off to translators.

@dsn5ft
Copy link
Contributor Author

dsn5ft commented Nov 18, 2015

sounds good, thank you!

@bluk
Copy link

bluk commented Nov 18, 2015

Cardholder Name seems good to me.

@dsn5ft
Copy link
Contributor Author

dsn5ft commented Nov 19, 2015

Sounds good, I can merge in my branch which renames everything to Cardholder Name

@dsn5ft
Copy link
Contributor Author

dsn5ft commented Nov 30, 2015

@braebot @bluk our Android and iOS pull requests are now updated with the correct translations, please let us know if there is anything else outstanding before they can be merged in. thank you!

@braebot
Copy link
Member

braebot commented Dec 2, 2015

Thanks @dsn5ft! I will put it through a few tests (including one in TestDroid), and merge/release when done.

@braebot braebot merged commit d784c9f into card-io:master Dec 2, 2015
@braebot
Copy link
Member

braebot commented Dec 2, 2015

Merged! Feel free to add yourselves as contributors in the readme in another PR, since I forgot to comment about that before merging. 🏆

@dsn5ft
Copy link
Contributor Author

dsn5ft commented Dec 3, 2015

will do. thanks!

This pull request was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants