Skip to content
This repository was archived by the owner on Dec 15, 2022. It is now read-only.

Conversation

@morfey911
Copy link

No description provided.

@morfey911 morfey911 changed the title AnimatedTextInputFieldConfigurator -> added 'email' text input type AnimatedTextInputFieldConfigurator -> added 'email' text input type & ability to change password type with or without disclosure Oct 12, 2016
Copy link

@danielmartin danielmartin left a comment

Choose a reason for hiding this comment

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

Thanks for your contribution! I wonder if it is easy to add a test covering this configuration. /cc @victorBaro @fillito


static func generate() -> TextInput {
static func generateWithDisclosure(visible: Bool = false) -> TextInput {
let textField = AnimatedTextField()

Choose a reason for hiding this comment

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

If the default for visibility is false, you could call this as generateWithDisclosure() and not get a disclosure button, which is confusing.

Copy link
Author

Choose a reason for hiding this comment

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

I agree, but this configurator is private, so i don't think it's a big problem. Whatever it was this types was helpful in my product, suddenly someone else come in handy.

@victorBaro
Copy link
Contributor

Hello @morfey911
Thank you again for contributing. We have added big changes in our latest release, 0.4.0, including an email text input type.
Could you please update your code and fix the conflicts so we can review again your features?
Thanks

@surajHT
Copy link

surajHT commented Dec 29, 2016

Hello @victorBaro
Can you add a option to have TextInputs, without the disclosure button or clear button? My requirements match the above criteria. It would be helpful if you could have it.

Thanks

case standard
case password
case passwordWithDisclosure
case passwordWithoutDisclosure
Copy link
Contributor

Choose a reason for hiding this comment

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

I like to have the passwordWithoutDisclosure case, but leave password as it was so we do not modify existing api

case password
case passwordWithDisclosure
case passwordWithoutDisclosure
case email
Copy link
Contributor

Choose a reason for hiding this comment

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

Update your branch, there is an email case already in 0.4

@victorBaro
Copy link
Contributor

Hello @surajHT
Please fix conflicts, see comments and we will merge.

Now that I have reviewed your code, it makes sense your suggestion of removing the clear button in TextInputs.

@victorBaro
Copy link
Contributor

@surajHT any updates on this?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants