We have a new helper function within scripts: `DynSelect_` Dynamic Select helps you to create a sel
We have a new helper function within scripts:
DynSelect_
Dynamic Select helps you to create a select field with dynamic options:
- Options within the select field can dynamically change based on input arguments.
- Support for TypeScript and Python.
- Conditional logic within the function to filer and sort select options based on specified conditions.
Changelog: https://www.windmill.dev/changelog/dynamic-selectDynamic Select
Dynamic Select is an helper function within scripts that allows you to create a select field with dynamic options.
18 Replies
We've made our runtime that we've called "REST" and "nativets" supports npm packages and relative imports! There is now no difference in the syntax of typescript/bun scripts and native scripts. Native scripts still only support a subset of what node support (just the fetch operation) but many npm packages can still be used because that's all they use under the hood (for instance, windmill-client and axios).
How to activate ? Just add
//native to the head of your script. Windmill will automatically convert between 'nativets' and 'bun' scripts based on the presence of this header so you can always just pick Typescript (bun) and decide at the end if you want to accelerate it with 'native' if possible.
We've also changed the default docker-compose/helm template to go from 4 small native workers with each 1 subworker to 1 bigger native worker with 8 subworkers as it performed better in our benchmarks. If you need more throughput, simply increase the replicas of the native workers, don't increase the number of subworkers past 8 as the interleaving will result in lower throughput.
This is a huge improvement as you can now make our native runtime an implementation details and we can unify everything under the standard "Typescript" language without anything windmill specific. Legacy native/fetch scripts will still work but the new REST button now simply prefill a bun script with a //native header.
native runtime is great for scripts that are doing simple fetch and require little compute but are io-bound on the response from the api. You can get parallelization of 8 requests/scripts at a time with a single worker, resulting in 8x better throughput between bun and native scripts at scale.Unknown User•3mo ago
Message Not Public
Sign In & Join Server To View
We fixed one of the most annoying bug of the frontend code editor of apps, types are no more overly narrowed to their literal types which mean you do not get erroneous squiggly error anymore for comparison and assignments, before vs after:
container group fields are now mutable internally, so you can start building reusable component groups with more stateful inner logics
New options for approval/suspend steps: Continue on disapproval/timeouts
Instead of failing the flow and bubbling up the error, continue to the next step which would allow to put a branchone right after to handle both cases separately. If any disapproval/timeout event is received, the resume payload will be similar to every error result in Winmdill, an object containing an
error field which you can use to distinguish between approvals and disapproval/timeouts
New option for flow error handlers: recover the flow if
recover: true is returned as part of the error handler result, also we standardized step_id to be in the default template
We added a vim mode to the code editors 🙂
On the app editor, you can now hide left, right and botom panels with special button or shortcuts
https://www.windmill.dev/changelog/hide-show-app-panels
Hide / Show App Editor Panels
Hide panels on App Editor with buttons and shortcuts.
Scripts and flows can now be triggered by the delivery of an email!
We'll be showing more today at 6 p.m. CET in our first weekly demo.
https://www.windmill.dev/changelog/email-triggers
https://www.windmill.dev/docs/advanced/email_triggers
Major: See service logs directly in windmill:
See the logs of any workers or any servers in the service logs of the search modal. Log count is seen in the mini-graph and error count is in red
you can now edit directly the yaml of flows within the flow editor
Major: windmill CLI (wmill) installable with npm and nodeJs compatible
We've made the CLI more accessible by being directly installable from npm:
npm install -g windmill-cli. It is now the recommended setup but the deno way will continue to work for the foreseable future. We updated the git sync examples as well: https://github.com/windmill-labs/windmill-sync-example/blob/main/.github/workflows/push-on-merge.yaml
There are no changes, the command is still wmill, and you will still be able to upgrade it with wmill upgrade (but require to deno uninstall wmill && npm install -g windmill-cli first)
One focus of this quarter is to improve the on-boarding experience and reduce the steep curve to learn windmill.GitHub
windmill-sync-example/.github/workflows/push-on-merge.yaml at main ...
Contribute to windmill-labs/windmill-sync-example development by creating an account on GitHub.
you can now easily change the id of steps in flows and it will modify every step inputs that depend on it automatically
We've improved the vscode extension handling of relative paths:
- On python it will detect that you're using relative paths and warn you that
wmill sync push is required
- On typescript we're introducing a beta mode that will actually bundle the relative paths as part of the preview to avoid the need of using wmill sync push as you're developing the common logic in parallel to your script logic
We fixed paste on macos on the vscode extension (you will need to update your instance to latest)
If you updated Windmill between friday evening and now, there is a bug that will make Date arguments of bun/deno scripts be passed to the script as strings instead of Date. Update to latest release 1.398.1 to fix. Apologies for this.
Hey! You can now set progress of execution of jobs from within the script. That is the feature specifically designed for long-running jobs to help You keep track of execution of your code. You can read more in docs: https://www.windmill.dev/docs/advanced/explicit_progress
Ansible Support
If you were here last friday you've already seen it, we're now supporting Ansible as a language!
We're very excited to see what can be acomplished by integrating Ansible into the Windmill ecosystem, so feel free to send all your feedback!
https://www.windmill.dev/docs/getting_started/scripts_quickstart/ansible
Ansible Quickstart | Windmill
Windmill Scripts