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

UL&S: Site Address tableView and continue button #294

Merged
merged 16 commits into from
Jun 2, 2020

Conversation

mindgraffiti
Copy link
Contributor

@mindgraffiti mindgraffiti commented Jun 1, 2020

Ref. #283
Ref. wordpress-mobile/WordPress-iOS#14230

This PR removes the temporary label, adds the tableView, and adds the continue button. The SiteAddressViewController now inherits from the LoginViewController so that it can pick up the submitButton behaviors found in NUXViewController.

To test

  1. Check out this branch
  2. bundle exec pod install
  3. build (with no errors)
  4. Check out the referenced PR to test changes: UL&S: Add tableView and continue button to SiteAddressViewController WordPress-iOS#14230

@mindgraffiti mindgraffiti added the enhancement New feature or request label Jun 1, 2020
@mindgraffiti mindgraffiti self-assigned this Jun 1, 2020
self.emailLoginInstructions = emailLoginInstructions
self.jetpackLoginInstructions = jetpackLoginInstructions
self.siteLoginInstructions = siteLoginInstructions
self.siteAddressPrimaryButton = siteAddressPrimaryButton
Copy link
Contributor

Choose a reason for hiding this comment

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

This seems to indicate we're going to have a string for every button on every view. That seems a bit excessive. Does the button text need to be customized? And to this level of granularity? It looks like host apps will typically use the same text for the same actions.

If we do need to customize the button text, I'm wondering if maybe we can have more generic strings, like continue, done, openMail , i.e. customize the text for the action instead of the view.

What do you think?

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'm overthinking it. More generic names for strings sounds better to me!

Copy link
Contributor

@Gio2018 Gio2018 left a comment

Choose a reason for hiding this comment

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

Just a thought about WordPressAuthenticatorDisplayStrings: does it need to be public? It seems that it is used by WordPressAuthenticator but not by the consumers of the library. Or maybe I'm just missing something

@mindgraffiti
Copy link
Contributor Author

@Gio2018 WordPressauthenticatorDisplayStrings needs to be public because other host apps set their own strings. Here's an example in WCiOS. Unfortunately when I created the WordPressauthenticatorDisplayStrings struct, I made it opinionated by setting WPiOS strings as the default. I don't know how to un-do that and build it better, but I'm definitely open to suggestions.

@Gio2018
Copy link
Contributor

Gio2018 commented Jun 2, 2020

@Gio2018 WordPressauthenticatorDisplayStrings needs to be public because other host apps set their own strings.

Ok then, I was missing something 🙂

@Gio2018 Gio2018 self-requested a review June 2, 2020 18:16
Copy link
Contributor

@Gio2018 Gio2018 left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@ScoutHarris ScoutHarris left a comment

Choose a reason for hiding this comment

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

Other than one nitpick about the string comment, looks good! Tested with wordpress-mobile/WordPress-iOS#14230.

:shipit:

siteLoginInstructions: NSLocalizedString("Enter the address of the WordPress site you'd like to connect.",
comment: "Instruction text on the login's site addresss screen."),
continueButtonTitle: NSLocalizedString("Continue",
comment: "The primary call-to-action button text on the unified site address screen.")
Copy link
Contributor

Choose a reason for hiding this comment

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

This comment should probably be generic.

@ScoutHarris
Copy link
Contributor

Oh, I just noticed the podspec version wasn't update. Probably should be 1.18.0-beta.3.

@mindgraffiti
Copy link
Contributor Author

Thank you for the reviews @Gio2018 and @ScoutHarris!

@mindgraffiti mindgraffiti merged commit e67b58c into develop Jun 2, 2020
@mindgraffiti mindgraffiti deleted the feature/283-site-address-ii branch June 2, 2020 18:48
@mindgraffiti mindgraffiti mentioned this pull request Jun 2, 2020
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants