Skip to content
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

Future of bindonce #126

Open
no-more opened this issue Nov 3, 2015 · 3 comments
Open

Future of bindonce #126

no-more opened this issue Nov 3, 2015 · 3 comments

Comments

@no-more
Copy link

no-more commented Nov 3, 2015

Hi,

First of all, thanks a lot for this great plugin. It saved my life on a previous project.

This is not an issue but a question (I'm not sure where I should post it).

I was wondering with new releases of angular (1.4, 1.5 and even 2.0) is there any case where we should still use bindonce ? I'm not an expert of the new angular native bindonce feature, does it cover all the features of bindonce ? If not, could someone explain the differences, and use cases ?

And the second question is: if there's still some case where we should use bindonce, will it be maintained? It seems the project is not active anymore.

Thanks a lot, and if you moved on another project I wish you the best.

@TheWrongAlice
Copy link

I think I was looking for an answer to this as well. I found this in the Angular documentation, and was wondering if bindonce has any advantage over it: https://docs.angularjs.org/guide/expression#one-time-binding

@hydrosquall
Copy link

^was wondering as well about native one-way binding vs using this library! Will test both.

@maxfriedmann
Copy link

Any updates on this @hydrosquall? I just stumbled over both (this neat directive and the "official" one-time-binding). Would be interested in exactly your outcome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants