ash_json_api
ash_json_api copied to clipboard
ash-project
The JSON:API extension for the Ash Framework
I don't think we'll want to implement a "user facing" aspect to ash core errors, so we'll need to write an adapter that turns ash errors into user presentable errors.
This is probably multiple issues, but we need to confirm spec compliance and behavior via tests.
We should validate that each include path is actually a valid path through the resource's relationships.
Currently the json schema does not support everything and is not quite finished. We should audit the current json schema endpoint and ensure that it is feature complete.
Right now, relationship routes use changeset level escape hatches like `Ash.Changeset.append_to_relationship`. What we should do, instead, is require that an action exists that accepts the relevant input. This allows customizing...
Working on implementation for issue https://github.com/ash-project/ash_json_api/issues/17, allowing users to define the strategy for how to handle keys with multiple words in types, relationships and attributes. I've implemented camelCase (userName) and...
Currently, everything is `snake_case` but we want to let users configure a name transformer at the API level, to turn everything into kebab case or camelcase.
Right now that validation is left to ash core, but it would be great to include it in the json schema.
There was something in place for short period, but it was insufficient and was removed. We should support writing to and reading from join table via the `meta` field on...