Repository navigation
getFeatures pagination failure #129
Description
Activity
Taking a look at this today. Thanks for reporting.
@zanetaylor this should now be resolved by changes on the felt side, no SDK changes necessary. Can you please test this in your app, and let us know if you're still having problems?
If it's all good, I'll close this issue.
If you are still seeing problems, it would be helpful if you could provide an example of the exact SDK calls that are not working as expected, along with the map ID that you're operating on so we can test directly.
Thanks!
Thanks @tomhicks! Sorry for the slow follow up, but I had a chance to test and confirmed that the default pagination seems to work as expected now. However, I'm still seeing the error with an explicit
pageSize. The map ID ismE0rS0umSaeQpOIsqaBbfAand the SDK call looks like this:felt.getFeatures({ layerId: 'lD8YQjgIRRSPAgsEz6Rs3A', select: ['target_blockid20', 'low_stress', 'high_stress'], pageSize: 50 }))
When attempting to construct an array of features in a pagination loop, I'm encountering perhaps related problems with the
pageSizeandpaginationparams for thegetFeaturesmethod.pageSizeparam always throws apostMessageconsole error: Error fetching features: could not convert string to float: ''pageSizeparam, the method returns the first 20 features as the expected default, but passing the response'snextPagekey to subsequent calls always returns the same / first 20 features instead of the next page.