Implement getMetadata count/index correctly #2

josh opened this Issue Feb 8, 2017 · 0 comments


None yet

1 participant

josh commented Feb 8, 2017

The current getMetadata endpoint doesn't respect the count or index (limit/offset) parameters to correctly return paginated results. I'm unsure, but this likely leads to a display bug on the controller reported by

Documentation reference:

@josh josh added a commit that closed this issue Feb 8, 2017
@josh Fix getMetadata pagination
Fixes #2
@josh josh closed this in 3de3b67 Feb 8, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment