Zach Daniel

So I've switched the underlying code to use this new `fetch` style. We will solve separately for the `more_previous?` concept in #334

This was solved in 64b3312cb94869d3ef9b25a11658e056c7191380

Yep! Accidentally commited. Fixed now.

This would be a good example of a change we could make for the 2.0 release and include in the upgrade guide

This has bee completed, its been changed to `append_and_remove`

This looks great so far! Awesome work! A couple notes: 1.) I think we want them to be able to optionally specify a context, and if they do that, the...

Now that I think of it though, lets call the param `--api`.

And when creating an api, it can just have an optional name, such that `mix ash.gen.api` makes `lib/myapp/api.ex` and `mix ash.gen.api context` makes `lib/myapp/context/context.ex`

One more thing: I think we also want to split the extension specific parts into the actual extension repo. So what we would do is say something like: ```elixir AshPostgres.DataLayer.resource_template(...options)...

I like the idea of having a specialized template, but it *might* be better to have it in the same template, something like `--with-guides`, that way we don't have to...