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

Disable log in after sign up #365

Merged
merged 8 commits into from
Jan 10, 2017
Merged

Disable log in after sign up #365

merged 8 commits into from
Jan 10, 2017

Conversation

cocojoe
Copy link
Member

@cocojoe cocojoe commented Dec 29, 2016

Generic notification presenter added
Assets added
Tests added

@cocojoe
Copy link
Member Author

cocojoe commented Dec 29, 2016

simulator screen shot 29 dec 2016 09 46 21

messageLabel.textAlignment = .center
messageLabel.font = regularSystemFont(size: 15)

switch(status) {
Copy link
Member

Choose a reason for hiding this comment

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

Why don't we have this logic in the status itself?

import Foundation

enum NotificationStatus {
case signedup
Copy link
Member

Choose a reason for hiding this comment

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

Should it be signedUp?

if self.options.loginAfterSignup {
login.start { self.handle(result: $0, callback: { callback(nil, $0) }) }
} else {
callback(nil,.noLoginAfterSignup)
Copy link
Member

Choose a reason for hiding this comment

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

This is hardly an error and we should have a better to switch screens

@hzalaz hzalaz modified the milestone: 2.0.0-rc.2 Dec 30, 2016
Generic notification presenter added
Tests added
Now instead of Results we have a different callback for event type:

- auth
- cancel
- error
- signup (wip)
- forgotPassword (wip)

They will work mostly as events, and some of them can be triggered in the same
lock run, e.g. auth & signup.
Also renamed internal results to better reflect the action that triggered it.
@hzalaz hzalaz force-pushed the feature_login_after_signup branch 2 times, most recently from 8914401 to 97aad7e Compare January 10, 2017 03:09
@hzalaz hzalaz merged commit 43a640d into v2 Jan 10, 2017
@hzalaz hzalaz deleted the feature_login_after_signup branch January 10, 2017 03:35
@hzalaz hzalaz changed the title Feature to disable log in after sign up Disable log in after sign up Jan 10, 2017
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.

2 participants