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

Added mustAcceptTerms option for Sign up #503

Merged
merged 2 commits into from
Jun 5, 2018
Merged

Conversation

cocojoe
Copy link
Member

@cocojoe cocojoe commented May 24, 2018

Updated i18n Strings
Update README
Added Tests

Updated README
@cocojoe cocojoe requested a review from lbalmaceda May 25, 2018 10:24
@cocojoe
Copy link
Member Author

cocojoe commented May 25, 2018

simulator screen shot - iphone x - 2018-05-23 at 16 00 09

@cocojoe cocojoe added this to the v2-Next milestone May 25, 2018
Copy link
Contributor

@lbalmaceda lbalmaceda left a comment

Choose a reason for hiding this comment

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

I see you already have the setters for customizing the privacy policy and terms URL. Where are those links accessible from? I don't see the text above the sign up button having a link color, nor the new dialog (introduced in this PR) having buttons or links to them.

@@ -244,6 +244,15 @@ class InputField: UIView, Stylable {
return 0
}
}

var isValid: Bool {
switch self {
Copy link
Contributor

Choose a reason for hiding this comment

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

is this normal? switching for a boolean seems way more complicated than just storing a "valid/!valid" boolean

Copy link
Member Author

@cocojoe cocojoe Jun 4, 2018

Choose a reason for hiding this comment

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

So by default you can't do that, unless you override and add comparisons for equality operators (which is annoying) as you need to specifically add for each case.
So in this case for clarity added this.

@@ -121,6 +121,10 @@ class OptionsSpec: QuickSpec {
it("should have allowShowPassword enabled") {
expect(options.allowShowPassword) == true
}

it("should have mustAcceptTerms disabled") {
expect(options.mustAcceptTerms) == false
Copy link
Contributor

Choose a reason for hiding this comment

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

is this test testing the "default value" ?

Copy link
Member Author

Choose a reason for hiding this comment

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

yes

@cocojoe
Copy link
Member Author

cocojoe commented Jun 4, 2018

@lbalmaceda you can access those from the main screen at the bottom.

@lbalmaceda
Copy link
Contributor

@cocojoe

you can access those from the main screen at the bottom.

where? this is not a link
image

@cocojoe
Copy link
Member Author

cocojoe commented Jun 5, 2018

@lbalmaceda It may not look like it, but it is, agree it could look more obvious, it's always been like this though.

@cocojoe cocojoe merged commit 162030f into master Jun 5, 2018
@cocojoe cocojoe deleted the added-accept-terms branch June 8, 2018 13:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants