Airplane lets you transform scripts, APIs, and SQL queries into tasks and UIs for your team in minutes. If you have feature requests you'd like to see in future changelogs, reply and let us know!
Since our last changelog, we've rolled out task-backed forms in Views and added fallback environments in Studio.
Task-backed forms in Views
Forms can now be backed by tasks. A task-backed form will automatically retrieve a task’s parameters and execute it when submitted. Try it out by adding <Form task="your_task_slug" /> to your view!
Fallback environments in Studio
You can now reference remote tasks, resources, and config variables from Studio if they do not exist locally. To get started, you can run airplane dev --env [fallback-env], where [fallback-env] is the slug of the environment you would like to fallback to. Check out the fallback environments docs for more information!
Improvements and fixes
- Even more Views components. We’ve added several new components for Views! You can now use the date and time picker, chip, number input (with currency and percent support), switch, description list, callout, slider, tabs, avatar, and code input in Views.
- Notification muting. We’ve improved our notification system to reduce the number of emails and Slack messages you receive. You'll no longer receive messages about run failures when you're actively looking at the run page. If you'd like to double-check your notifications, you can always check the Airplane inbox where all notifications are delivered.
- Studio improvements. We’ve made various improvements to the local Studio experience. We rolled out support for file parameters (use these in a local task or file input component), Slack, and JavaScript templates (JSTs). This means that any JSTs inside your task will be interpreted properly.
