Skip to content

Conversation

@kadamwhite
Copy link
Collaborator

Parameters are more generic than filters: they can be useful on almost any API resource if they are used to specify context or to trigger data embedding. Moving these from CollectionRequest means that they will also be available on WPRequest derivatives like the paging .next and .prev requests, enabling consumers of the pagination queries to utilize methods like .embed().

Parameters are more generic than filters: they can be useful on
almost any API resource if they are used to specify context or to
trigger data embedding. Moving these from CollectionRequest means
that they will also be available on WPRequest derivatives like
the paging `.next` and `.prev` requests, enabling consumers of
the pagination queries to utilize methods like `.embed()`.
@kadamwhite
Copy link
Collaborator Author

TODO: move the corresponding unit tests from CollectionRequest's suite to WPRequest's

This re-unites the tests with the object on which they are defined
@kadamwhite kadamwhite merged commit 449548f into master Jan 22, 2016
@kadamwhite kadamwhite deleted the move-params-and-renderquery-to-wprequest branch January 22, 2016 01:55
@kadamwhite
Copy link
Collaborator Author

Done moving unit tests; merged branch

@kadamwhite kadamwhite mentioned this pull request Jan 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants