We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Why do devs have to touch this at all? It's already a custom element, why not have the smarts built in?
Proposed behaviour:
for
<gold-cc-input>
<form>
<iron-form>
It should, practically, also solve #18 (as it's very rare for a user to enter the CVC before the card number).
The text was updated successfully, but these errors were encountered:
I don't think tying them together needs to be that complicated. Since cardType is a notify property, you can just do something like:
cardType
<gold-cc-input auto-validate card-type="{{cardType}}"></gold-cc-input> <gold-cc-cvc-input amex="[[_computeAmex(cardType)]]"></gold-cc-cvc-input>
I realize that's a bit annoying, however, so I'll change gold cc-cvc-input to have a cardType property instead of amex, so that you can just write:
gold cc-cvc-input
amex
<gold-cc-input auto-validate card-type="{{cardType}}"></gold-cc-input> <gold-cc-cvc-input card-type="{{cardType}}"></gold-cc-cvc-input>
Sorry, something went wrong.
No branches or pull requests
Why do devs have to touch this at all? It's already a custom element, why not have the smarts built in?
Proposed behaviour:
for
attribute, which takes a selector for a<gold-cc-input>
element.<form>
,<iron-form>
, or non-<form>
first parent also has a single<gold-cc-input>
as a child, then bind to thatIt should, practically, also solve #18 (as it's very rare for a user to enter the CVC before the card number).
The text was updated successfully, but these errors were encountered: