-
Notifications
You must be signed in to change notification settings - Fork 643
Replace <XSelect>
component with regular <select>
element
#2037
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
Conversation
We could also consider using https://github.com/jmurphyau/ember-truth-helpers instead if we start to use this more and/or need other, related helpers
@@ -0,0 +1,7 @@ | |||
import { helper } from '@ember/component/helper'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's gonna be so good to have this helper as part of the framework :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
seems like a straight-forward change. interesting how XSelect was only used in one spot
@bors r+ |
📌 Commit 8e1714b has been approved by |
Replace `<XSelect>` component with regular `<select>` element We've only been using `XSelect` in one specific place and v3 of the addon was causing deprecation warnings due to their use of the `this.$()` API. Since we were not using any of the more advanced features from `XSelect` it was relatively straight-forward to replace with just a regular `<select>` element. r? @locks
☀️ Test successful - checks-travis |
We've only been using
XSelect
in one specific place and v3 of the addon was causing deprecation warnings due to their use of thethis.$()
API.Since we were not using any of the more advanced features from
XSelect
it was relatively straight-forward to replace with just a regular<select>
element.r? @locks