I have a page which contains pagedArray, populated by many local models (filtered).
My UI allows a user to initiate an edit model, where they can update properties on the model.
When the model is updated, the pagedArray still displays the old result.
Is this a configuration issue on my part (i.e when properly configured, should pagedArray automatically update?), or a missing feature in the add-on?
After looking through issues, it seems that https://github.com/mharris717/ember-cli-pagination/issues/183 may be related, but the proposed solution seems hacky. Ideally any system component which updates a model shouldn't be coupled to the implementation details of the pagedArray - this is what the store is for...
I have a page which contains pagedArray, populated by many local models (filtered).
My UI allows a user to initiate an edit model, where they can update properties on the model.
When the model is updated, the
pagedArraystill displays the old result.Is this a configuration issue on my part (i.e when properly configured, should pagedArray automatically update?), or a missing feature in the add-on?
After looking through issues, it seems that https://github.com/mharris717/ember-cli-pagination/issues/183 may be related, but the proposed solution seems hacky. Ideally any system component which updates a model shouldn't be coupled to the implementation details of the pagedArray - this is what the store is for...