render_api 0.1.1

Unofficial Dart client for the Render REST API, covering workflows, tasks and task runs. Not affiliated with or endorsed by Render.

0.1.1

Documentation and packaging; no API changes.

• The README's usage example did not compile. It described an earlier hand-written facade — render.taskRuns.run(...), render.workflows.list(), waitFor — none of which exist on the generated API. Rewritten around what the package actually exposes, and every snippet now verified by compiling it.
• Adds example/example.dart, and formats the package. Those were the two things costing pub.dev points; the score is now 160/160.
• tool/generate.dart runs dart format as its last step, so regenerating cannot undo the formatting.
• The README now points at the two companion packages: render_workflows for running tasks, and render-dart on npm for writing the task bodies in Dart. pub.dev serves the README from the published archive, so this needed a release to become visible.

0.1.0

Initial release.

• The whole Render REST API: 208 operations and 164 models, generated from Render's OpenAPI specification.
• Two spellings of every call — flat (render.listWorkflows(...), matching Render's own Node examples) and grouped (render.raw.workflows.listWorkflows(...)).
• Method names taken from the spec's operationId, so they correspond one for one with Render's official @api/render-api bindings.
• Typed exceptions carrying hints for Render's less obvious responses — 500 rather than 404 for an unknown task run id, and 500 for a workflow whose repository cannot be read.
• Unknown enum values decode to .unknown rather than throwing, so a new region or status cannot break a working client.
• Cursor pagination, retries with backoff, and a configurable timeout.
• Runs on the Dart VM and under dart2js. On the web there is no environment, so the API token must be passed explicitly.