beekeeper 0.3.0

Summary

Batching and rate limiting.

Proposal wording

• Add documentation for implementing batching and rate-limiting.
• If possible, export functionality to help implement these processes, but standards seem to vary widely.
• Potential challenges: This step will involve more reading and documenting than code, to gather examples of how different APIs implement limits and batching. It's possible systems will be so different that it will be difficult to summarize them. For example, Slack has two separate batching systems in its API, with some functions moved to the newer system, and others not.

Changes from proposal

• This was actually developed after 0.4.0.
• The wording I really wanted here was "pagination."
• This milestone resulted in the pagination vignette.

What's Changed

• Update for rapid function renames. by @jonthegeek in #42
• Refactor code to prep for paths by @jonthegeek in #43
• Implement simple paths by @jonthegeek in #44
• Scrub temp paths. by @jonthegeek in #45
• Paths for FEC by @jonthegeek in #47
• Generalize for trello. by @jonthegeek in #48
• Update README with path functionality. by @jonthegeek in #49
• Properly test for security. by @jonthegeek in #50
• Use split version of nectar::call_api by @jonthegeek in #53
• Pagination by @jonthegeek in #54

Full Changelog: v0.2.0...v0.3.0