search

quarkiverse / quarkus-renarde

Server-side Web Framework with Qute templating, magic/easier controllers, auth, reverse-routing
Apache License 2.0
74 stars 19 forks source link

"rest"-package #6

Open simeonlin opened 2 years ago

simeonlin commented 2 years ago

Of course it's "just" a convention and only a small detail.. But I don't think that "rest" is the right package-name for a controller-class of a webapp.

And another small detail: The link to the user documentation in the readme is not working. I found it under https://github.com/quarkiverse/quarkus-renarde/blob/main/docs/modules/ROOT/pages/index.adoc. And it was really helpfull!! 👍

(If an issue on this project is not the right way to provide feedback: just let me know!)

FroMage commented 2 years ago

Well, I couldn't think of anything better than rest. What did you have in mind?

simeonlin commented 2 years ago

Why not controllers? REST is an architectural style for web-apis. Of course, my controller-class can come close to the constraints of REST. But i don't think it should be the goal of renarde to make this connection between renard-controllers and REST as a convention.

(As a small example where I wouldn't like to follow the convention: I work on a project where we extend our quarkus-rest-backend with a simple web-client for admin purposes with qute. And REST is everywhere in the project. We share REST-Ressources and implement REST-Clients.. But the controllers of the web-client don't have a lot to do with REST here.)