Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

api/transactions orderBy uses non standard prefixing #166

Closed
ByronAP opened this issue Jun 1, 2016 · 1 comment
Closed

api/transactions orderBy uses non standard prefixing #166

ByronAP opened this issue Jun 1, 2016 · 1 comment
Assignees
Milestone

Comments

@ByronAP
Copy link

ByronAP commented Jun 1, 2016

example: https://liskwallet.info/api/transactions?senderId=3870520582125084358L&orderBy=height:desc
response: {"success":false,"error":"Failed to get transactions"}
expected: {"success":true,"transactions":[Array of transactions],"count":"9"}

@ByronAP
Copy link
Author

ByronAP commented Jun 4, 2016

The documentation is wrong it shows orderBy=field yet if you read the fine print it says that it should be orderBy=t_field, adding the t_ prefix makes the request work however it breaks the standards of the api as no other request requires this.

@ByronAP ByronAP changed the title api/transactions orderBy fails api/transactions orderBy uses non standard prefixing Jun 4, 2016
@karmacoma karmacoma added this to the Version 0.3.2 milestone Jun 8, 2016
@karmacoma karmacoma added the ready label Jun 8, 2016
@fix fix self-assigned this Jun 10, 2016
@fix fix added in progress and removed ready labels Jun 10, 2016
@karmacoma karmacoma modified the milestones: Version 0.3.3, Version 0.3.2 Aug 9, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants