Skip to content

getFeatures pagination failure #129

@zanetaylor

Description

@zanetaylor

When attempting to construct an array of features in a pagination loop, I'm encountering perhaps related problems with the pageSize and pagination params for the getFeatures method.

  1. Using an explicit pageSize param always throws a postMessage console error: Error fetching features: could not convert string to float: ''
  2. Without an explicit pageSize param, the method returns the first 20 features as the expected default, but passing the response's nextPage key to subsequent calls always returns the same / first 20 features instead of the next page.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions