API Pagination Question

[cbunge]

Pagination with our API. Is the expectation to parse the meta return for total vs current and determine the remaining page loop? Most have a header or a data value for nextlink. I guess I’ve always been lazy on ours with a -1 or something. Trying to figure out the cleanest way to paginate.

[#2]

-1 will be getting removed

[#3]

make that a big bold red warning in the docs please

[#4]

if you passed an offset greater than the total, it would loop forever

[#5]

looks great on mobile?

[#6]

I dunno…but the pattern is sound

[#7]

didn’t think about an increase during runtime

[#8]

was going to post it

[#9]

Oh…yeah, good catch

[#10]

We should start doing that in 5.5 actually

[#11]

it’s definitely going to break stuff, but I know it’s the proper way to do it

[#12]

probably should be >= intstead of == 

[#13]

ie. a bunch of records got deleted right before you send your last request

[#14]

https://blog.2bitcoder.net/paging-morpheus-api-in-python/

[#15]

if nextResult['meta']['offset'] + nextResult['meta']['size'] >= result['meta']['total']

[#16]

I have a powershell script that pages

[cbunge]

@ncelebic gotta increase that column width

[#18]

correct, no nextlinks with morpheus