Async iterator pagination

[aspilchen]

Thank you for helping out! ✨

We really appreciate your commitment to improving Architect

To maintain a high standard of quality in our releases, before merging every pull request we ask that you've completed the following:

• Forked the repo and created your branch from master
• Made sure tests pass (run npm it from the repo root)
• Expanded test coverage related to your changes:
  • Added and/or updated unit tests (if appropriate)
  • Added and/or updated integration tests (if appropriate)
• Updated relevant documentation:
  • Internal to this repo (e.g. readme.md, help docs, inline docs & comments, etc.)
  • Architect docs (arc.codes)
• Summarized your changes in changelog.md
• Linked to any related issues, PRs, etc. below that may relate to, consume, or necessitate these changes

Please also be sure to completed the CLA (if you haven't already).

Learn more about contributing to Architect here.

Thanks again!

[aspilchen]

TODO:

• Handle errors

Extra notes:

• Current version requires paginate param to be a string, plugin validation enforces bool

[aspilchen]

aws-lite/src/request/index.js

Line 268 in bebf88c

if (foundNestedToken && (foundNestedToken !== params[type][cursor[i]])) {

Throws error if params[type] does not exist

[ryanblock]

aws-lite/src/request/index.js

Line 268 in bebf88c

if (foundNestedToken && (foundNestedToken !== params[type][cursor[i]])) {

Throws error if params[type] does not exist

Got it, interesting this hasn't come up, but that's why unit tests are nice. :)

I'm thinking if params[type] then perhaps we need to backfill it earlier in execution, like params[type] = params[type] || {}?