-
Notifications
You must be signed in to change notification settings - Fork 11
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
Changes from 7 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
7372328
Merge branch 'develop' into feature/283-site-address-ii
mindgraffiti e28d75d
Add a tableview and a NUXButton below the tableview
mindgraffiti 00cb0c2
Attach the tableView and continueButton outlets
mindgraffiti 333b819
Connect tableview delegate and datasource
mindgraffiti fff9f7c
Change the continue button to be a primary NUX button
mindgraffiti c2063a9
Add siteAddressPrimaryButton title to DisplayStrings struct
mindgraffiti c787d48
Inherit from the LoginViewController
mindgraffiti a1a010c
Change the display text to be more generic
mindgraffiti 4f98172
bump the podspec
mindgraffiti cf90a80
Quick sketch to lay out a few example tableview cells
mindgraffiti dfd7f4f
Add table row cells and conform to NUXKeyboardResponder
mindgraffiti 4af1f3d
Revert "Add table row cells and conform to NUXKeyboardResponder"
mindgraffiti e80c672
Revert "Quick sketch to lay out a few example tableview cells"
mindgraffiti d357666
Revert "bump the podspec"
mindgraffiti 412f0ec
Bump podspec
mindgraffiti 42fef10
Change comment text for translators
mindgraffiti File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 a problem hiding this comment.
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?
There was a problem hiding this comment.
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!