Skip to content

improve TextField example screen #618

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

Merged
merged 2 commits into from
Jan 15, 2020
Merged

Conversation

ethanshar
Copy link
Collaborator

@ethanshar ethanshar commented Jan 13, 2020

I separated the text field screen to 3

  • General Inputs - what we have today
  • Custom Inputs - showing different custom UI styling
  • Input Validation - show the (new) validation functionality in depth

This is just the initial work, but from here we can start re-arrange the input examples better.
It will also help when we'll add e2e tests

@@ -41,22 +41,22 @@ export default class InputsScreen extends Component {
message = 'Please enter a valid text';
}
this.setState({error: message});
Copy link
Collaborator

Choose a reason for hiding this comment

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

If there is a dedicated screen for validations why not clean this screen from all error examples to keep it simple?

Copy link
Collaborator

Choose a reason for hiding this comment

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

Cool. So you want to merge it like that or after the cleanup?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Done. I'll make it more simple in the future, for now I move the error/validation examples

import {Navigation} from 'react-native-navigation';
import {KeyboardAwareInsetsView} from 'react-native-keyboard-tracking-view';

class InputValidationsScreen extends Component {
Copy link
Collaborator

Choose a reason for hiding this comment

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

Don't you want to add an useTopErrors example? Maybe a toggle button to switch between the top and the bottom error like in the input screen?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

done

@ethanshar ethanshar requested a review from Inbal-Tish January 14, 2020 14:50
@Inbal-Tish Inbal-Tish merged commit eee164e into master Jan 15, 2020
@ethanshar ethanshar deleted the infra/improve_input_screen branch May 17, 2020 07:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants