Closed
Description
At ICATT, we find we sometimes need to talk to the Umbraco backend endpoints directly, in cases where functionality exists in the backend, but is not implemented in Heartcore yet. For instance, we use this endpoint to properly handle redirects:
https://{projectAlias}.s1.umbraco.io/umbraco/backoffice/UmbracoApi/RedirectUrlManagement/SearchRedirectUrls
Do you have a strategy for exposing these kind of functionalities throught the dotnet client? If properly encapsulated, functionalities like this could be offered via the backend at first, and then be rerouted to proper Heartcore endpoints in due time, without breaking clients.
If this aligns with your strategy, we could work on a PR for the SearchRedirectUrls endpoint.
Metadata
Metadata
Assignees
Labels
No labels