Daniel Kukula
Daniel Kukula
ok thanks. I just watched the beginning of the video and you had the images folder in separate disectery than the markdown files
I ended up with enum type in postgres and keep my enums in a list-takes a bit more space but its easier to maintain.
I started playing with that and came with an initial sketch, currently all in one file `lib/mix/tasks/ash.ex` It would be good to get some opinions on that before I continue....
This can accept an --context param, this is not a problem. I can do this over the weekend. I need also split it to separate files, and move the templates...
ok, thanks for the suggestions
When I think now about it and we can have the postgres specific task in the ash-postgres repo so if its not installed it won't even show up in the...
ok, no problem. I need to check how this is all done in phoenix.
This is more or less usable. Feels a bit pythonic, that's my background the largest file is generated with this command: `mix ash.gen.resource users --json-api --graphql --postgres --policy-authorizer name age...
@zachdaniel the template per package needs to be a separate file: ``` defmodule AshPostgres.Templates do def resource_template(assigns) do """ postgres do repo #{assigns.project_name}.Repo table "#{assigns.table_name}" end """ end def guide_template(assigns)...
Ok, I'm thinking to make Ash.Template behaviour so its standarized.