-
-
Notifications
You must be signed in to change notification settings - Fork 81
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
Deprecation in 1.13.8 #66
Labels
Comments
I'm seeing the same thing |
Interesting. I'll try to take a look tonight. If not first thing tomorrow |
same thing, and
|
Robdel12
added a commit
that referenced
this issue
Aug 14, 2015
This fixes #66. I ended up having to move the way we register x-option with it's parent component into an ember after render run loop.
Sorry about that! We should be depreciation free now. |
Awesome, thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just upgraded to ember 1.13.8 and I'm seeing the following deprecation notice from emberx-select:
I'm getting one deprecation notice for each option tag in the select. My template is:
I'm using the head of master, as recommended. I even tried
rm -rf node_modules ; npm cache clean ; npm install
to verify I was REALLY getting the latest, but no luck.My package.son has
"emberx-select": "thefrontside/emberx-select",
The text was updated successfully, but these errors were encountered: