Refactor URL endpoints

[christianlupus]

Some of the endpoints are not well named or well structured. An example is given in this issue discussion.
The endpoints should be reworked and used correctly throughout the app.

[seyfeb]

As I see it, we have have as our main data models Recipes and (considering #340) Cookbooks (in the future), and maybe Categorys and Keywords. What do you think about allowing the creation of categories and keywords without any recipes assigned?

I would then propose to have endpoints for (most) CRUD operations on these objects. There are other things one may like to use for filtering recipes such as cooking time, ingredients, tools, author, language, ... but they probably should be included as additional information and not become separate endpoints.

In the Nextcloud documentation on routing there is an example for a resource which exposes endpoints to

• Get all entries
• Get one entry by id
• Create an entry
• Update an entry
• Delete an entry

This is currently used for the recipes, although, at the moment, the MainController contains some recipe-related stuff as well, which is handled by the RecipeController. I guess most of it is old and unused and requires some cleanup (also in routes.php unused routes should be removed).

At the same time I would propose to create separate Controllers for each of our resources to get a clearer structure in the code base.

[christianlupus]

What do you think about allowing the creation of categories and keywords without any recipes assigned?

Then we need to rework the database first (see #300).

At the same time I would propose to create separate Controllers for each of our resources to get a clearer structure in the code base.

Definitively. This is part of the refactoring process of the codebase.
We should also consider moving to versioned API endpoints sooner than later (especially before any stable V1.0). Then we can have legacy controllers if the API endpoints need to change anytime in the future.