When running a paginated query, the offset is forced to the value calculated for the page. If an offset is set in parameters or in the query type itself, it will get overwritten by the pagination methods.

This prevents from using the offset to split a list of items into different fields.

Any offset that is predefined in the query field should be added to the values used for pagination.

Example:
Blog container that has Blog post children. The blog type has two query fields:

• highlighted_post : returns the most recent blog post, using an offset of 0 and a limit of 1
• posts: all blog posts except the highlighted one, using an offset of 1

posts should always ignore the first item, and its items count (used in pagination) should always be the total minus 1.