feat(validity): add new html5 validity to component #68

[jason-capsule42]

Alaska Airlines Pull Request

Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.

Fixes: #68

Summary:

This PR adds HTML5 validation functionality to mirror functional changes made to other auro form element components.

Type of change:

Please delete options that are not relevant.

• [x] New capability
• [ ] Revision of an existing capability
• [ ] Infrastructure change (automation, etc.)
• [ ] Other (please elaborate)

Checklist:

• [x] My update follows the CONTRIBUTING guidelines of this project
• [x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.

Thank you for your submission!
-- Auro Design System Team

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

:white_check_mark: jason-capsule42
:x: Jason Baker

---

Jason Baker seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[jason-capsule42]

The only bug I saw was in the "Disable individual checkboxes w/ required" example that we spoke about. Other than that, all of the other validity work looks good.

Turns out this was a documentation example issue rather that a code bug. This is cleaned up and review re-requested.

[blackfalcon]

There is an inconsistency I am seeing with the error attr. With other elements when the error attr is added, validity="customError" is added as well. Also, when error is removed, validity="customError" is removed also. That is not happening in the demo.

[AuroDesignSystem]

:tada: This PR is included in version 1.2.0 :tada:

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: