In an HstComponent, create an HstLink using the parent mount of the current mount of HstRequestContext and set it to a model through HstRequest#setModel(…). Then, it will be shown in a model of the component.
Or do you need another way or different use cases?
That works fine, but I was looking for a solution on the API or configuration level.
I understand that from the CMS perspective it makes sense to render links to the “resourceapi/” OOTB, but in SPAs that is not applicable since these links are going to be consumed by the frontend and it’s not very practical to be stripping out the “resourceapi”. With this solution, the backend code will have to render all the links to the parent mount, which feels a bit strange.
Also in a multi-channel set-up is it the parent always the Site mount?