-
Notifications
You must be signed in to change notification settings - Fork 160
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
Indexes are not changing #16
Comments
OK, there's no issue at all. The problem is that I'm loading sortablejs before the observable populates the model. This observable is obtained from a webservice call, therefore it is a timing issue I have to solve in my code. Sorry for the inconvenience of my not issue. |
Hi @thybak should be fixed with the latest version |
I'm waiting NPM to release your 1.2.1 version. Once it's published I'll answer you if my original problem can be solved without initializing the array property in the model. Thank you, @smnbbrv |
Hi @thybak , sorry for delay, now it should be published. Try again, please |
Works like a charm! Good job 👍 Thank you again for your work and the SortableJS team too, @smnbbrv ;) |
First of all thank you for your work. I guess that this module is being useful for everybody here.
I have to say that I read your readme carefully before writing this issue. But, although I was able to install this module and I could make changes client-side, these changes are not reflected in my model property, which is an object array. I followed your instructions by using [sortablejs]='-propertyName-' in the template, but it had no use for me. After changing the order of the elements, the array has the elements in the same position of the beginning in the model property, not in the view (where, in fact, they've changed).
Since I found this problem, I tried a workaround by using the SortableJsOptions. However, inside the event functions you don't have the same context of the Angular Component and you can't modify model properties.
I ran out of possibilities here, am I losing something in my reasoning?
The text was updated successfully, but these errors were encountered: