←
HashtagsPublic conversations
PUBLIC CONVERSATIONS

#ashframework

Read the latest public tweets for a hashtag.

20 tweets on this page for “#ashframework”

Elixir Forum avatar
Elixir Forum@elixirforum·Nov 16

[Ash] [Phoenix] [Dev Profile] Oliver Banoub - Cairo, Egypt (Remote) – Elixir/Ash backend dev contract forum.elixirforum.com/t/7739… #ashframework #phoenixframework #elixirlang #myelixirstatus

Zach Daniel avatar
Zach Daniel@ZachSDaniel1·Nov 5

#ashframework (more specifically the underlying DSL library Spark) support just landed in Expert LS! github.com/expert-lsp/expert… Huge shout out to @dorgan_, this is a huge QoL improvement for #ashframework users ❤️ #elixirlang

Elixir Forum avatar
Elixir Forum@elixirforum·Nov 3

[Ash] [Nerves] [Phoenix] [Event Chat] Code BEAM Europe 2026: all four keynotes are on YouTube forum.elixirforum.com/t/7724… #ashframework #nervesproject #phoenixframework #elixirlang #myelixirstatus

Zach Daniel avatar
Zach Daniel@ZachSDaniel1·Nov 2

The moatless.store MCP now exposes UI components as resources, thanks to the features from #ashframework's AshAi package. It is really fun when I get to play with the tools that I build for others, and get to feel the insane speed up and power of an integrated set of tools 😎 AshAi docs: ash-ai.hexdocs.pm/readme.htm…

0:19
Elixir Forum avatar
Elixir Forum@elixirforum·Oct 31

[Ash] [Announcing] AshBilling – Declarative Stripe billing and subscriptions for Ash Framework forum.elixirforum.com/t/7721… #ashframework #elixirlang #myelixirstatus

Zach Daniel avatar
Zach Daniel@ZachSDaniel1·Oct 19

Coming soon: MCP tools for #ashframework's AshAi package. Specifically, while it's been trivial to create an MCP server, integrating your own tool loop with an external MCP server has been something you had to figure out yourself. It ships with OAuth client management resources that you can generate with `mix ash_ai.gen.mcp_oauth`. Recently shipped: - Tool approval flows and pausing flows, allowing you to dynamically require approval, and provide the approval result to the chat. - Support for tools that generate image content parts

Post attachment
Zach Daniel avatar
Zach Daniel@ZachSDaniel1·Oct 14

Introducing: Ash.Signals 😎 Signals are a way to model complex side effects in large #ashframework applications. They provide a typed contract and compile time guarantees, and can dramatically help when building applications with complex and interconnected domains. Check out the explainer! ash-hq.org/blog/introducing-…

Post attachment
Zach Daniel avatar
Zach Daniel@ZachSDaniel1·Oct 11

Core team member and "getting shit done" extraordinaire @sevenseacat just completed a full rebuild for ash-hq.org into a static site 🥳 The #ashframework website has a pretty interesting history. It started out as a Google site. I just wanted to get something simple out the door. Then, it began to become a sort of "universal target" for every batty idea I had. We needed an example application, so why not rebuild the website with all kinds of features, kill two birds with one stone? Except it never really acted as a good example because it's not the sort of thing you actually build with Ash. I wanted to experiment with some alternative data layers. Oh, what if we killed two birds with one stone and made a blog data layer that stores data in markdown files and can be edited from AshAdmin? Except I never really made it a great blog experience (or wrote that many blog posts). Ash docs weren't great, and ex_doc really didn't provide great mechanisms for documenting DSLs. Two birds! Let's make our own documentation site that aggregates across our hex packages, is searchable and indexed! Except everyone was used to hex and we just ended up maintaining two documentation sites, and as I contributed to ex_doc and as they got around to multi-package search, our separate docs sites became a burden, not a benefit. The list goes on. A good reminder that sometimes you should just be satisfied with the one bird.

Zach Daniel avatar
Zach Daniel@ZachSDaniel1·Oct 10

Cooking up a cool feature for #ashframework designed to help with large applications with lots of interconnected domains. Right now you end up with actions that chain actions and side effects through hooks, creating dependencies just because the initiator needs to be where the code lives. Example code in the image. I've got a pretty great way to invert this, removing cross-resource dependencies and making it much easier to understand "what does what" in your Ash application. And its declarative and in a way that is easy to verify at compile time 😎 Should be ready soon.

Post attachment
Zach Daniel avatar
Zach Daniel@ZachSDaniel1·Oct 10

Still gotta hand it to @mikehostetler. Went hunting to see if #ashframework's AshAI package supports OpenAI's decision model, and of course ReqLLM already supports it and its perfectly compatible with what we built on top of it

Zach Daniel avatar
Zach Daniel@ZachSDaniel1·Oct 8

Super useful feature of #ashframework is policy breakdowns. Ash can explain exactly why a user was or wasn't allowed to perform an action, with no need for you to do anything aside from write your policies 🧠. It naturally falls out of the declarative model of policies.

Post attachment
Zach Daniel avatar
Zach Daniel@ZachSDaniel1·Oct 5

I'm pleased to announce #ashframework's newest core team member: @maennchen_ ! He has been a steadfast partner for well over a year now, and has helped secure the Ash ecosystem (and to a much greater degree the Elixir/BEAM ecosystem as a whole). He also built an entire CNA platform with Ash 😎

Show more tweets