ash-project/ash_phoenix
1
0
Fork 0
mirror of https://github.com/ash-project/ash_phoenix.git synced 2024-09-20 07:12:49 +12:00
Code Issues Projects Releases Packages Wiki Activity

docs: change getting started directory structure to match realworld (#78)

Browse source
This commit is contained in:
Axel Baudot 2023-03-09 21:46:54 +00:00 committed by GitHub
parent 3caecf30de
commit 022e3a3c0a
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
documentation/tutorials/getting-started-with-ash-and-phoenix.md
View file

@ -138,7 +138,7 @@ An Ash registry points to one or more resources. In our case we will only have a
For now take a look at the `Blog` API and the `Blog.Registry`:
```elixir
# lib/my_ash_phoenix_app/blog.ex
# lib/my_ash_phoenix_app/blog/blog.ex
defmodule MyAshPhoenixApp.Blog do
use Ash.Api
@ -177,16 +177,16 @@ It's convention to place all the resource in their own resources folder. So when
lib/
├─ my_ash_phoenix_app/
│ ├─ blog/
│ │ ├─ blog.ex
│ │ ├─ registry.ex
│ │ ├─ resources/
│ │ │ ├─ post.ex
│ ├─ blog.ex
```
Below is the resource module. Read the comments carefully, every line is explained:
```elixir
# lib/my_ash_phoenix_app/blog/post.ex
# lib/my_ash_phoenix_app/blog/resources/post.ex
defmodule MyAshPhoenixApp.Blog.Post do
# Using Ash.Resource turns this module into an Ash resource.