Jose Carvajal

As far as I see it, the use case here is to individually customize the child entities' resources (sub-resources). For example, users want to secure the parent resource with the...

> This doesn't ring true to me. In my experience, admins in small shops have every permission, while other users are restricted access based on ownership/permissions of the resource itself,...

PR description updated with more details about the changes and the use case.

Yep, documenting this extension is a must-have. I only found this limitation because I wanted to try something in one of my examples.

I would not like to block these changes due to the lack of documentation on this extension, which should be done sooner than later in a separate pull request. What...

At the moment, in Resteasy classic we can define links using unexisting fields. Example: ```java @GET @Path("/get/{slugOrId}") @Produces({ MediaType.APPLICATION_JSON, "application/hal+json" }) @LinkResource(rel = "get by slug or id", pathParameters =...

> Huh, I guess this got added after I contributed that functionality. What is the purpose of returning `http://localhost:8081/records/get/slugOrId` to the client? That URI is invalid. I don't understand the...

> OK, so RESTEasy classic is not doing this right, and you're proposing to return a URI template as a link. Fine, I can imagine this being useful. To get...

@FroMage I've just updated the documentation of the Resteasy Reactive Links.

@FroMage I've reverted the changes in the documentation and added a sentence explaining these changes. About using JSON for the web links, there is already a section for this: https://quarkus.io/guides/resteasy-reactive#json-hypertext-application-language-hal-support