-
Notifications
You must be signed in to change notification settings - Fork 310
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
Order of operations matters when using computed properties and a formatter #658
Comments
The idea of |
In fact, the only usage of |
@jccazeaux mikeric/sightglass#16 is merged, but I'm not sure how to release. |
Should we change the docs on computed properties to make it clear that it doesn't need to be used if you are using |
To release sightglass it must be pushed in npm as a |
It is also on bower and component – shall we just ignore them? |
We should keep the version up to date in all the repo. Is sightglass really used outside rivets? |
I use it outside rivets 😛 |
@Leeds-eBooks has sightglass been published? |
No, will do it asap |
OK, package.json must be updated to use it for the |
Yeah I guess I'll have to publish |
Ah, totally didn't know that bower fetches the latest version from github automatically! |
Ok updated sightglass is bundled in |
Specifying the computed property dependency before a number formatter and the
| call
results in the property not being recomputedhttps://jsfiddle.net/64ta6qzz/18/
The text was updated successfully, but these errors were encountered: