ash-project/ash_postgres
1
0
Fork 0
mirror of https://github.com/ash-project/ash_postgres.git synced 2024-09-20 05:23:18 +12:00
Code Issues Projects Releases Packages Wiki Activity
A postgresql datalayer for the Ash Framework
6 commits 40 branches 326 tags 13 MiB
Elixir 100%
Find a file
Zach Daniel a52218b772
WIP
2019-11-24 19:01:54 -05:00
config move datalayer stuff into its own repo 2019-10-06 16:36:18 -04:00
lib WIP 2019-11-24 19:01:54 -05:00
test move datalayer stuff into its own repo 2019-10-06 16:36:18 -04:00
.formatter.exs move datalayer stuff into its own repo 2019-10-06 16:36:18 -04:00
.gitignore move datalayer stuff into its own repo 2019-10-06 16:36:18 -04:00
mix.exs move datalayer stuff into its own repo 2019-10-06 16:36:18 -04:00
mix.lock move datalayer stuff into its own repo 2019-10-06 16:36:18 -04:00
README.md stateful relationship actions 2019-11-02 16:37:13 -04:00

README.md

AshEcto

TODO: Add description

TODO LIST (in no order)

  • Determine if we want to own the dependency of ecto. If not, somehow have a compatibility determination step at compile time
  • Add the ability for a data_layer to express what it can/can't do, so the engine can adjust accordingly. I don't want runtime failures as a result of this, I want Ash/frontends to say what they need from the data layer at compile time, so DSL elements that would result in failure behavior are detected at compile time.
  • support through relationships, here and in ash