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

Fallback to "-text-field" component name for unrecognized input type #11004

Conversation

bantic
Copy link
Member

@bantic bantic commented May 1, 2015

Previously, using an input type not in the map (such as {{input type="email"}}) would
cause an exception. This renames the classification var to more
expressive componentNameMap, and turns the map into a whitelist for
non-default component names only. Any value of "type" not in that map (or
no value for "type") will use the default "-text-field" component name.

Previously, using an input type not in the map (such as "email") would
cause an exception. This renames the `classification` var to more
expressive `componentNameMap`, and turns the map into a whitelist of
non-default component names only. Any value of "type" not in that map (or
no value for "type") will use the default "-text-field" component name.
@bantic
Copy link
Member Author

bantic commented May 1, 2015

(Note: This PR is for the idempotent-rerender aka "Glimmer" branch)

wycats added a commit that referenced this pull request May 1, 2015
…ypes

Fallback to "-text-field" component name for unrecognized input type
@wycats wycats merged commit 505ec73 into emberjs:idempotent-rerender May 1, 2015
@mixonic mixonic deleted the idempotent-rerender-fix-input-types branch May 1, 2015 22:14
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.

4 participants