Special Thanks

The Core Team

You’ve all done amazing work, and your help and support is instrumental to Ash’s success.

• @jimsynz
• @barnabasJ
• @joshprice
• @rgraff

The community

While there are too many folks to name, I’d like to highlight a few who have made an especially large impact lately.

• @vonagam | Consistently provides excellent pull requests (often fixing bugs that I personally added )
• @rbino | Upgraded AshGraphql to support Ash 3.0, one of the largest/most complex upgrades required!
• @dblack | Upgraded AshPhoenix to support Ash 3.0.

If you’ve been contributing but didn’t get a shout out, please know your contributions are not any less valuable. This only works because we’re all working towards a shared goal, and it’s an amazing privilege to be rowing in the same direction as so many fine folks. I’m currently investigating more ways that we can recognize community members for their great work

Alembic

Alembic is funding the time of myself, @jimsynz and often other Alembians to work on Ash. Their willingness to put their money where their mouth is shows not only their conviction that Ash is a better way to build software, but also the calibre of their team. They are putting Ash through its paces on tons of ambitious projects, which drives many of the benefits and improvements that Ash users receive! I’m beyond grateful for their support and expertise.

ElixirForum

I’d like to make a special callout to the fine folks running this forum, and the community here. A few months ago we made the choice to focus our support efforts here on ElixirForum. This was unequivocally a good choice! Not only has it helped increase the discoverability of Ash in general(via its wildly good SEO), it also makes sure that our support efforts don’t disappear behind a walled garden. We still have our discord server, and it is a great place to chat and interact with the Ash community, but we encourage users to ask questions here on the ElixirForum primarily. This community is well moderated, kind and helpful! A community is always representative of its leaders, and so I’d like to thank @AstonJ and others for their excellent stewardship.

In fact, now that we’ve got 300 threads we’ve been upgraded to a full 3-section Ash Forum, with dedicated sections for News, Chat, and Questions!

Screenshot 2024-04-02 at 02.57.58221×140 5.63 KB

Please check out our upcoming events as well! We’re giving a training that will be updated for Ash 3.0 at ElixirConf EU and Gig City Elixir

ElixirConf EU:

https://www.elixirconf.eu/trainings/ash-framework/

Gig City Elixir:

https://www.gigcityelixir.com/training

I have just reminded that there’s ash_events repository, but it looks like it did not had much attention for over a half year and it’s also not ready for production yet. Are there any plans to finish this project and make it compatible with 3.x version?

Cool stuff. I’ve been wanting to try out Ash again, but have been waiting for the new release to give it a shot. Looking forward to it for sure!

I will update it for 3.0 Its a very small library, it can be copied into folks apps. Until I or someone else wants to use it in production, it will probably stay in its current state.

Congratulations !

Ash seems interesting, I don’t know much about the framework but the book is something I would definitely be interested in

Congrats on the RC of Ash 3 It’s been fantastic seeing its progress here on the forum and you and the Ash team have done a great job onboarding people by answering their questions quickly and comprehensively

Also great to see you managed to get Dave to publish an Ash book for us all! I am sure it will be very popular!!

It’s also fantastic seeing the Elixir eco-system expanding with projects like Ash - it marks a new level of maturity for the language and I am sure will help with the next phase of adoption. So thank you and the Ash team (and all other similar projects) for your hard work

Just upgraded my codebase from 2 to 3.0 RC18 and figured I would leave feedback. Didn’t see any other thread for this. It took me 2 hours WITH EXTENSIVE TESTING for a codebase with ~20 resources spread out over 3 domains.

First off, WOW y’all changed a lot. Do you sleep?

I figured I would just upgrade without RTFM because I am a typical developer. That did not last long. Like 2 minutes. So just RTFM. Though, even after I read, I am pretty sure I am still not doing things the “ash” way, or as Zach intended.

For mix.ex, took the simple path and just pointed at github:
{:ash, github: “ash-project/ash”, override: true},
{:ash_postgres, github: “ash-project/ash_postgres”, override: true},
{:ash_authentication, github: “team-alembic/ash_authentication”, override: true},
{:ash_authentication_phoenix, github: “team-alembic/ash_authentication_phoenix”, override: true},

I love the change to domains.

Adding public? to pretty much everything was tedious, but fine. I didn’t realize I needed to add it to all my “belongs_to” as well, and that led to some broken pages. I am not using either json or graphql apis, so I am not worried (yet).

I have an “archived_at” field that should never be changed outside of a specific destroy action, and it had “private?” which no longer exists. Instead of figuring out how to deal with it, I simply removed that restriction, and moved on with life.

I added “default_accept :*” to all resources because it just seemed easier than figuring out how to match my existing code.

Again, added “require_atomic?” to pretty much all :update actions, because again, a few resources needed it, and i just didn’t want to figure out all that needed it, so I went the easy route and just did them all. Not what Zach intended, but I didn’t want to learn the intricacies of the atomic stuff.

COMPILING IS SIGNIFICANTLY SLOWER. Like painfully slow. If I change a resource, it used to be maybe 5s, and now I am usually over 20s waiting. My guess is some cyclic issue that I need to use the mix task to locate. Luckily, resources don’t change too often.

Something in VScode now bombs on my most complex resource, “deadlocked waiting on module MyApp.MyModule” (renamed here) and this never happened before. I close VScode and reopen.

If I forget to add a field to public or part of the accepted list, then I still get:

[error] GenServer pid<0.5936.0> terminating
** (AshPhoenix.Form.NoFormConfigured) fields at path must be configured in the form to be used with inputs_for. For example:

which is the most useless error. It takes me a few min to realize the real issue. Would love if that finally is addressed.

I just want an easy way to load calculations of an embedded resource. External stuff shouldn’t know certain fields are “special” and need to be loaded. Am I missing some option on a calculation to load by default?

No joke, you need to retest literally everything in your app. Absolutely ever page, action, email, whatever. Literally everything was broken for me.

Great work though! Good luck everyone!

Hey there! Thanks for the feedback! In the latest release candidate, I added a compatibility option to help with the upgrade. Couple things:

1. require_atomic?

config :ash, :require_atomic_by_default?, false

Its listed in the upgrade guide (in the rc after you started upgrading) as something to allow you to upgrade without worrying about that step.

2. public?: true

Agreed, it is tedious but worth it IMO.

3. default_accept :*

Yep, much easier to do that, and then go back and address if you feel like it

4. compile times

Let’s chat about this. Definitely want to address this. If this is something that is caused by the upgrade, we need to work it out. Things should be faster not slower, so please if you get some time, let’s run through what could be causing that.

5. no form configured

This is really interesting, I think that we could absolutely give a better error here. Specifically, we can add some hint text at the bottom, that checks

• is there a private attribute w/ this name
• is there a relationship w/ this name
• is there an argument w/ this name

and it can hint to you what the problem might be. I’ll look at that shortly.

6. loading calculations of embedded resources

Add this to your embedded resource:

changes do
  change load([:your, :things, :that, :always, :load])
end

preparations do
  prepare build(load: [:your, :things, :that, :always, :load])
end

EDIT: error hints for NoFormConfigured errors have been added, will be available in the next release of ash_phoenix improvement: add error hints for `NoFormConfigured` errors · ash-project/ash_phoenix@1f511de · GitHub

EDIT: oh, and adding require_atomic? false is totally cool Learn about atomics when you have the inclination/time. We’re also working on better docs that explain how they work. Check the rc docs for actions and changes to see more.

I think Zach missed replying to this one, but public? is the inverse of private?. public? defaults to false, so you are automatically getting the equivalent of private?: true. You can explicitly set public?: false if you want, but it’s not needed.