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

feat(alert): input validation #12541

Conversation

dudeofawesome
Copy link
Contributor

@dudeofawesome dudeofawesome commented Aug 1, 2017

Short description of what this resolves:

Add user-friendly input validation for Alert dialogs.

Changes proposed in this pull request:

  • Add ability to do Angular form validation inside Alerts.
  • Add 'submit' role to AlertButton. This allows for disabling form submission when the form is invalid.
  • Converts Alert form to a Reactive Form.
  • Improve type definition for AlertOptions.
  • Use @HostBinding decorator, per Angular Style Guide.
  • Fix a few typos in already existing alert documentation.

Ionic Version: 3.x

Fixes: #12540 #7819 #5916

dudeofawesome and others added 30 commits November 27, 2016 23:52
When `Tabs` are nested within each other, the highlight can get
misaligned. This prevents that by ensuring the affected
`.tab-highlight` is a direct child of the targeted `Tabs`.
…tabs

* wip

* wip

* progress

* wippy skippy

* getting there

* all tests passing except goBack

* unit tests pass again boi

* goBack tests pass

* great success

* the good stuff
This is by [recommendation from the Angular Style
Guide](https://angular.io/guide/styleguide#hostlistenerhostbinding-decor
 ators-versus-host-metadata)
This allows the Angular TypeScript Language Service to tell editors how
to highlight and lint the template properly, as well as making editing
and reading the template much simpler.
They now set min and max values, instead of min and max lengths.
@Ionitron
Copy link
Collaborator

Hello and thank you for contributing to Ionic! We have been working on porting all of the Ionic components to web components and have recently updated master to reflect this. This significant change has caused this pull request to break. While we really appreciate the time and effort you put into creating this, we are not able to merge it because of the newly introduced conflicts. We are extremely sorry about this. We will not be merging any more features in to v3. If this is a feature and you have the time, please resubmit this PR against the master branch. If this is a critical security issue in v3, we would greatly appreciate it if you would resubmit the PR against the new v3 branch. Thanks so much for your time!

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.