ember-cli-pagination | Pagination Addon for Ember CLI | Addon library

You need define the query params in both side Route and Controller.

app/routes/post.js

When I see zlib errors, I often need to either restart my ember server or clear my node_modules folder and re-install packages. Does that resolve things for you?

I finally found the error, the error was displayed when the component tried to set the new property.

The real problem was: when I attempted to save the property of the question some questions got "." and it seems to be that Ember.computed does not allow to use them for a property, so when I tried this.set('some.question.with.dots', '') the error was triggered and display the Property set failed.

The solution was simple, I only had to use .replace() function of javascript to replace all the dots in the string.

The final code is next:

The problem you had is most probably using ^ for your dependencies. What ^ (caret) does is upgrading your dependencies to a major version when you do a clean install. For instance if your dependency to an addon is let's say 1.2.0 and you used ^1.2.0 and there is a new version available 1.3.0, you will get this new major version. If you use ~ (tilda) instead of ^, then you will not get 1.3.0 but 1.2.2 for instance if available. In order to use the exact versions so that your dependencies will not change when you do a clean npm install, you can remove both caret and tilda in your dependency definitions.

In order to figure out which of your dependencies is outdated you can use npm outdated.

I would like to point out issues I found in posted code,

1.Inside list route model hook, you are trying to load list model from store by using peekAll and peekRecord and I haven't found the code to load list model to store.

Without doing findAll('list') if you do peekAll or peekRecord you will get nothing, since peekAll or peekRecord both will return whatever already loaded in store it will not fetch it from server.

So you need to load list model records into store. For this you can do it in beforeModel hook, or you can do it any one of the parent route