-
Notifications
You must be signed in to change notification settings - Fork 229
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
Added: refresh() function now accepts optional 'data' parameter which ca... #32
Conversation
… can affect the way the items are scrolled in the view.
Nice job. If i remember correclty, there were several people requesting a functionality like that. I saw some (commented out), can you remove them, and also copy the description of how your functionality works and paste it into the readme.md? i'll definitely merge it then, thanks. |
OK, I'll improve the readme and cleanup the code. I was also thinking about integrating the idea of #8, i.e. that the |
…g the way the items are scrolled in the view. Updated: README.md Comments cleanup.
Well, it took some time since I was busy but I updated the readme and I also incorporated a mechanism similar to the #8, i.e. the scrolling can be controlled also via directive attributes. I just renamed the settings: |
Great. One more thing. Could you not wrap my one-statement |
Done ;) |
Added: refresh() function now accepts optional 'data' parameter which ca...
There is is a bug #43 with the merged functionality. Is that an easy fix? |
Fixed in #44. |
Added: refresh() function now accepts optional 'data' parameter which can affect the way the items are scrolled in the view.
I added a functionality that I needed for my project. If you find it usefull also for you or the others, merge it into.
The functionality enhances the current behaviour. The user can trigger the 'vsRepeatTrigger' with additional data - an object with the following properties: