-
Notifications
You must be signed in to change notification settings - Fork 141
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 warnings with Ember 3.20 #402
Comments
Awesome, thanks for the heads up! Will take a look at that this week. |
maxfierke
added a commit
that referenced
this issue
Jul 22, 2020
Resolves a deprecation warning in Ember 3.20 Closes #402
@maxfierke any update on this? |
@boris-petrov it was breaking CI for some earlier Ember versions, but will look at relaxing the constraint a bit tonight to allow for a greater range of versions |
The maybe-in-element addon has recent v2 release as well. |
maxfierke
added a commit
that referenced
this issue
Aug 14, 2020
Resolves a deprecation warning in Ember 3.20 Closes #402
This has been addressed in v3.4.4 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This addon uses
ember-maybe-in-element
0.4.0 which uses the as-of-Ember-3.20 deprecated-in-element
. That's printed as warnings in the console when runningember serve
. Simply updatingember-maybe-in-element
to 1.0.0 should fix the issue.Thanks for the great addon!
The text was updated successfully, but these errors were encountered: