-
Notifications
You must be signed in to change notification settings - Fork 157
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
Task properties broken in canary #279
Comments
This PR refactors the Descriptor system in Ember metal, mostly replacing it with a Decorator system instead. `defineProperty` has been updated to apply decorators following the currently implemented spec. This means that the value returned by `computed` goes through the exact same flow when applied as a decorator using decorator syntax, and applied using classic syntax.
See #277 |
Also, for how to be compatible with multiple versions at once, we should use ember-compatibility-helpers, since it checks the Ember version at build time which allows us to completely strip out the unused version for folks who aren't using that version. |
Oh, nice, already in progress! Great, thanks for being so diligent and sorry for the extra noise! |
All good, private API changes like this are always a little tricky, and it's good to know when it's affecting people and for visibility in general 😄 |
Unfortunately I get this very error ( It originates from this line in and fails on this line: It has worked fine on Ember 3.8 (but that's probably not much help). |
@balinterdi I just run
and fix the problem. |
this commit changes the signature of
ComputedProperty
's constructor to accept an array, so this passes the wrong arguments and throws aTypeError: Found non-callable @@iterator
exception (although for some reason in CI I sawAssertion Failed: A computed property key must be a string, you passed undefined undefined
instead).I'm happy to take a crack at a PR to fix this, but I'm unsure of how. I'll leave a comment in that commit asking the core folks if they have a recommendation, but the only two options I can think of are:
try...catch
to invoke it one way, and on failure, try to invoke it the other way (seems pretty sketchy).Other ideas?
The text was updated successfully, but these errors were encountered: