Instances of page-numbers trigger errors with certain attribute orders

[jasonmevans]

I discovered this issue just now while implementing pagination in my project. The underlying stack trace and error messaging surrounding the issue were not clear, so I did a bit of digging into the ember source code. It seems that the way this project requires properties to be passed into the page-numbers component causes an exception when content does not come first.

ember-cli-pagination/addon/components/page-numbers.js

Line 9 in 9f43e32

currentPage: Ember.computed.alias("content.page"),

The reason being that on this line the currentPage property is a bound alias to content.page. Now, if currentPage comes before content you will receive a console error saying, "Property set failed: object in path "content" could not be found or was destroyed."

{{page-numbers currentPage=page content=results }}

If the order is changed to this then the error will be resolved:

{{page-numbers content=results currentPage=page }}

[Redsandro]

I'm experiencing the same, and similar issues the other way around.

Is there a similar ember-cli module that works with property names as used in the JSON:API documentation for pagination? I'm having to do a lot of guesswork for undocumented things (such as nested properties), so I would rather try something that works with zero configuration.