You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
I would suggest that you create a feature request for what you believe is missing from the APIs. More than happy to looking adding new capabilities, which can support your needs.
Using the Backoffice as per your example is not supported and can change with any future update.
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.
The text was updated successfully, but these errors were encountered: