I had to submit a support request to Airtable in order to discover that the API rate limit applies per base, not per API KEY. After that discovery I proposed documentation updates for them to clarify that.

Would you consider updating your docs as well to clarify that point for users of your wrapper? This affects teams with multiple collaborators on one base, all using the API concurrent

In the README, it shows examples of injecting Faraday middlwares at runtime. However, it's been deprecated to ad-hoc append to the middleware chain at runtime. We should instead create a proper API for configuring these middlewares. Both circuit breakers and retries are nifty, along with throttling.

This is a duplicate of #54, but I cannot re-open it. I have however discovered the culprit

The data being returned by Airtable is in the order according to the view, but the order is not respected by the call to Bluebird.map, which is noted in the official docs. This is true even when concurrency is set to 1.

I don't see any official way t

the compose.yml has the 0.9.5 flag.

If you moved to using dockerhub w/ the latest flag the yml wouldn't ever need manually updated.

Currently, plugin replaces all strings in the design doc.

Does it need a feature to replace only the strings on this page, or the strings contained in this node, or just the strings in a selection?