List Usability - List only returns up to 1000 about amplify-swift

[lawmicha]

I think this is P1 due to JS not recursively calling LLC when more than 1000 items

[jamesonwilliams]

I think we should decide on a consistent list/query paradigm across all of our categories. One possibility is to always return an iterator/iterable, so that we can do pagination under the hood, on behalf of the user, if they seek next() beyond a page boundary:

Amplify.Storage.list(
    bucketUri,
    iterator -> {
        while (iterator.hasNext()) {
            Log.i(TAG, "Item: " + iterator.next().toString());
        }
    },
    error -> Log.e(TAG, "Failed to get items from storage.", error)
);

If we don't do that, then we should provide the user with a way to handle their own pagination, and perhaps just give them back a collection/list:

Amplify.Storage.list(
    bucketUri,
    nextToken, // Nota Bien!
    listResults -> {
        // Pseudo-code to show some of the necessary fields in the `listResults`:
        final int pageNumber = listResults.getPageNumber();
        final String nextToken = listResults.getNextToken();
        final Collection<StorageItem> listResults.getItems();
    },
    error -> Log.e(TAG, "Failed to get any results.", error)
);

[lawmicha]

thanks for the comment, i've moved this over to pivotal and referenced this issue for the context. closing this out to track on pivotal