Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
generic pagination support page[xy] next to offset/limit
See original GitHub issueIs there a reason QuerySpec doesn’t support page[number]?
from the spec: Note: JSON API is agnostic about the pagination strategy used by a server. Effective pagination strategies include (but are not limited to): page-based, offset-based, and cursor-based. The page query parameter can be used as a basis for any of these strategies. For example, a page-based strategy might use query parameters such as page[number] and page[size], an offset-based strategy might use page[offset] and page[limit], while a cursor-based strategy might use page[cursor].
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:12 (10 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
just yesterday it was merged thanks to the PR of @vicmosin. I will also to some experiments with it and then do a release.
crnk API is still fairly compatible, altough QueryParams and some other things have been deprecated. The internal implementation is mostly rewritten (taking Katharsis 2.x as baseline).
Mega props, thanks @vicmosin and @remmeier 😄 That is such good news to hear 😃