Hi there, I'm currently working on integrating Ash into my existing Phoenix/Ecto/Postgres app. So far Ash looks amazing and seems to be exactly what I'm looking for - the power and balance of ecto but without having to create basic utility functions over and over and over again
Sorry if my question has already been answered, I couldn't find anything on GH, google, docs or Discord.
However I don't yet want to migrate all my existing Ecto (Phoenix Context) resources all at once, but go step by step. Now, I added a new Repo, Registry and API with a new resource and that works fine. However now I want to add a :belongs_to in my new resource's :relationships - and that needs to be a user, so the resource belongs to a user. Thing is, the User resource already exists as a normal Ecto schema that is used in my app, so ash tells me it can't find the resource. Is there some way to have a "compatibility" layer between an existing ecto schema and an ash resource?
The Elixir backend framework for unparalleled productivity. Declarative tools that let you stop wasting time. Use with Phoenix LiveView or build APIs in minutes for your front-end of choice.