You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On my current AngularJS project, we are integrating jsTree in a directive. It started pretty well, but very fast it became a nightmare. I can't recall half the problems we encountered, but we painfully ended up with a bunch of buggy, convoluted code. It would have been a better idea to just write our tree directive from scratch.
However, I just ran into a project I wish I had know about before :
It's exactly what we needed, it's pure AngularJS (which is a HUGE benefit, no more jQuery events to register to), and the creator is a well known and respected individual in the AngularJS community (the way I structure my apps owes him and his blog a lot).
In general it's not a good idea to wrap an existing jQuery-based library with an Angular directive, and it's especially true in this particular case. Save yourself the pain and go pure Angular.
The text was updated successfully, but these errors were encountered:
On my current AngularJS project, we are integrating jsTree in a directive. It started pretty well, but very fast it became a nightmare. I can't recall half the problems we encountered, but we painfully ended up with a bunch of buggy, convoluted code. It would have been a better idea to just write our tree directive from scratch.
However, I just ran into a project I wish I had know about before :
https://github.com/tchatel/angular-treeRepeat
It's exactly what we needed, it's pure AngularJS (which is a HUGE benefit, no more jQuery events to register to), and the creator is a well known and respected individual in the AngularJS community (the way I structure my apps owes him and his blog a lot).
In general it's not a good idea to wrap an existing jQuery-based library with an Angular directive, and it's especially true in this particular case. Save yourself the pain and go pure Angular.
The text was updated successfully, but these errors were encountered: