mirror of
https://github.com/ash-project/ash_postgres.git
synced 2024-09-20 05:23:18 +12:00
WIP
This commit is contained in:
parent
ea5c0edc87
commit
d6b8d280a2
1 changed files with 1 additions and 7 deletions
|
@ -1,9 +1,3 @@
|
||||||
# AshPostgres
|
# AshPostgres
|
||||||
|
|
||||||
**TODO: Add description**
|
**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
|
|
Loading…
Reference in a new issue