Right, so this is for editing the relationship, its /post/:id/relationships/comments. However, that isn’t for creating new things, I just reread your initial post and now I see what you mean. This should likely be done as POST /comments specifying a post id to be the most REST-ish. We can add the option to ignore the base-route for some routes, that way on comment you could do: create :create, route: "/post/:post_id/comments", base_route?: false and have it pass the post_id through.
zachdaniel
Creator of Ash
0
gordoneliel
Thats not bad. Although, would I have to have 2 create actions? When creating a Post, I create a Comment alongside through the managed relationship, but If I also want to create a Comment for a Post, I need another create action that specifies an argument post, :map, allow_nil? false.
Eg.
Comment resource:
create :create_direct do
argument :post, :map, allow_nil?: false
accept [...]
change manage_relationship(:post, type: :append)
end
create :create_managed do
primary? true
accept [...]
end
0
zachdaniel
Creator of Ash
You can simplify a bit if you do
belongs_to :post, Post do
attribute_writable? true
end
then they can provide the post_id directly as an input. Then
create :create do
accept [..., :post_id]
primary? true
end
And then use that one action in both. Since post_id is not nullable, you will always be prevented from creating a comment with no post, and the manage_relationship will set post_id automatically.
1