Accounts: Total Pages and Page does not make sense
Issue #2 wontfix
Currently, Accounts are defined as
Accounts: description: An optionally paginated array of accounts. type: object properties: Total: type: integer format: int32 description: Total number of results in this collection across all pages TotalPages: type: integer format: int32 description: Total number of pages Page: type: integer format: int32 description: Current page number Accounts: type: array description: An array of accounts with entity types dependent on the account type (deposit, investment, loan, or line of credit) items: $ref: '#/definitions/Account'
But it is a JSON data, and there is no notion of Page. So, Total Pages and Page does not make sense.
Propose to drop them.
OR define what is meant by Page.
Is there any use case for many pages accounts? (Edmund) > Anoop.
Anoop will come up with examples.
• This features enables servers to send the response in parts (chunks). • IF the account too many and the implementation of API that returns accounts and transactions. It might be daunting task for server to query & collect all data in one query result. • None of the implementation so far has shown interest in this. But is an optional feature added. • I am ok with removing if it is confusing. • Total Pages – total Number pages resulted for query • Total – Number of accounts records • Page - Current page number returned. • I will try to find ; if this can be represented in mock up example if we decide to add to FAPI.
Data specs no longer being worked on