allow manual validation

[notwaldorf]

Added a validate() function to the behaviour, and refactored the paper-input-container to get notified (and care) when the contained iron-input's validity changes. PTAL.

Needs PolymerElements/iron-input#13 to work.

[morethanreal]

It seems a little weird to me to have a validate function on <paper-input-container>, since it doesn't have validatable content but reflects the state of a validatable thing in its light DOM.

What do you think about calling validate on the input, which sets invalid (the property needs a notify:true in iron-validatable-behavior), and use binding to set the invalid property on the <paper-input-container>?

[morethanreal]

Or fire an event from iron-validatable-behavior that the container listens for to set invalid.

[notwaldorf]

Done!

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project, in which case you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please let us know the company's name.

[googlebot]

CLAs look good, thanks!

[morethanreal]

Only iron-input's have a validate method actually.

[notwaldorf]

ping?

[morethanreal]

Sorry, lgtm.

[govis]

So if one calls .setCustomValidity('Test error') on the underlying input (is="iron-input") as per original 0.5 doc - should it automatically trigger paper-input's invalid state and display the error message? Doesn't seem to be the case.

var pi = document.getElementById('test');
var i = Polymer.dom(pi.root).querySelector('input');
i.setCustomValidity('Test error');