[APIB-4282] OpenAPI spec has paging info for Associations/objectid #572
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Fiachra Shanahan <fiachra.shanahan@xero.com>
|
PETOSS-346 |
|
Thanks for raising an issue, a ticket has been created to track your request |
|
@rob-wigmore - In the developer documentation PR there is an example of the sort query param alongside a direction query param like this: Associations/{ObjectId}?sort=CreatedDateUtc&direction=DESC Should direction be added as an additional param in the spec here? |
…ations/objectid Co-authored-by: Fiachra Shanahan <fiachra.shanahan@xero.com>
Thanks for that, we have included direction in the latest commit. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
OpenAPI spec has paging info for Associations/objectid
Description
Paging information has been added to the OpenAPI spec on the associations/{objectid} endpoint
Release Notes
The endpoint was updated and the Open API spec needs to be updated to reflect the new functionality
https://xero.atlassian.net/browse/APIB-4282
Types of Changes