ash-project/ash
1
0
Fork 0
mirror of https://github.com/ash-project/ash.git synced 2024-09-19 21:13:10 +12:00
Code Issues Projects Releases Packages Wiki Activity
A declarative and extensible framework for building Elixir applications.
12 commits 93 branches 718 tags 29 MiB
Elixir 100%
Find a file
Zach Daniel d0362b65d7
move json_api out to ash_json_api
2019-10-11 11:06:09 -07:00
config move datalayer stuff out of ash 2019-10-06 16:36:06 -04:00
lib move json_api out to ash_json_api 2019-10-11 11:06:09 -07:00
test init 2019-10-02 23:08:36 -04:00
.formatter.exs adding includes support 2019-10-05 20:33:38 -04:00
.gitignore init 2019-10-02 23:08:36 -04:00
mix.exs move json_api out to ash_json_api 2019-10-11 11:06:09 -07:00
mix.lock updated the example, added the skeleton of "get" 2019-10-03 03:18:07 -04:00
README.md finish ash_ecto setup 2019-10-07 10:38:30 -04:00

README.md

Ash

TODO: Add description

TODO LIST (in no order)

  • Add central API configuration DSL api do ... end
    • Use this for default_page_size and max_page_size
  • Make our router cabaple of describing its routes in mix phx.routes Chris McCord says that we could probably power that, seeing as phoenix controls both APIs, and that capability could be added to Plug.Router
  • Finish the serializer
  • Make primary key type configurable
  • Make a DSL for join tables to support complex validation/hooks into how they work, support more than just table names in join_through
  • DSL level validations! Things like includes validating that their chain exists.
  • break up the Ash module
  • Wire up/formalize the error handling
  • Consider adding an expose do block inside of attributes that will be the same as defining an attribute but will automatically add expose?: true so developers don't have to type it all the time.
  • Ensure that errors are properly propagated up from the data_layer behaviour, and every operation is allowed to fail