This is an interesting approach. Thank you for sharing it with the community.
We monitor the feature requests in the portal, and if the community shows interest in having localization capabilities in the Breadcrumb, we will consider enhancing the component.
Progress is here for your business, like always. Read more about the measures we are taking to ensure business continuity and help fight the COVID-19 pandemic. Our thoughts here at Progress are with those affected by the outbreak.
Posted on:21 May 2020 17:47
Here's the full implementation of our current localized breadcrumbs. It is far from eloquent or robust but it works...for now.
--we build a list of localized key/values in the controller. Then hide the values on the page
Model.Breadcrumb is a simple string property that contains the breadcrumb values separated by a "/". ie "Human Resources/Employees/Edit".
It works as the component correctly separates the crumbs by the "/" but we have no control over the underlying href in the anchor without resorting to using a jquery hack in the DOM.
In an ideal world, it would be great if the .Value attribute would accept a key/value pair. The key being the href to use in the anchor and value be the string value to be displayed to the user. That would simply allow us to build the kvp using whatever means we want, localize the value and then simply pass the built kvp to the breadcrumb component. It would then use the value as the text for the li and the key would be used for the href for the anchor.