As a developer implementing a queryFeatures workflow for a feature layer that has not been added to the view, if a query would end up exceeding the max number of features allowed by the service, is it the responsibility of the developer to make subsequent queryFeatures calls to capture all features? That is, does the developer has to write the logic to to look at the "exceededTransferLimit" return value, and make subsquent calls implementing paging? Is there any way to have the SDK to this for you with one function call in the code resulting in however many network calls to get the full list of features? I know that's how it works when you're adding a feature layer to a map - you only have to write map.add(featureLayer) and the SDK just makes however many necessary calls it takes to get the features back. Was hoping this is how queryFeatures works as well, but my preliminary testing seems to indicate that is not the case.
Here is a codepen that shows what I'm talking about:
https://codepen.io/jaysgregory/pen/dyeKYYy
