This is a super quick, informal update about the goings on in and around Ash Framework. If you find something interesting and think it should make it on this newsletter, drop a message in the #ash-weekly channel in our Discord server.
Check out Ash Premium Support from Alembic.
Sponsor me if you like what I do.
Join myself and Josh in Braga, Portugal for our training at AlchemyConf 🎉! Use code ZACHDANIEL to get 10% off your ticket to the conference. Can’t wait to see you all there 😎. Really looking forward to this conference.
https://membrz.club/alchemyconf/events/supercharge-your-elixir-apps-with-ash
Since this is a pretty quiet week, I thought I’d leave you all with something fun! Maybe a bit more than a “teaser” though…
Allow manual read actions to return a `full_count`, which is used to inform pagination about how many total records there are in the data source.
Validate action types in `Ash` functions more eagerly. This prevents a few cryptic errors that would arise when an update action was passed in to `Ash.destroy`, for example.
Added a `mix reactor.run`, which allows you to run a reactor from the command line!
Added a `placement` option to `Igniter.Libs.Phoenix.add_scope/4` and `Igniter.Libs.Phoenix.append_to_scope/4`
Added `assert_has_task` test helper
Added `mix igniter.remove` for removing dependencies
Added `--skip-unknown` flag to `mix ash_postgres.gen.resources`
Added a `--no-migrations` flag to `mix ash_postgres.gen.resources
Added an `after_batch` callback for `RunObanTrigger`, bulk inserting all jobs required after bulk actions (using `insert_all` if you’re on Oban Pro)
Added `worker_module_name` and `scheduler_module_name` options, which solves for problems with renaming resources causing dangling jobs
Added `mix ash_oban.set_default_module_names`, a mix task for setting those module names automatically
No posts
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.