This is an old debate that finally got attention and got covered by an Epic which will be worked out: https://liferay.atlassian.net/browse/LPD-43161 Giulia Nobile, our Product Manager, will be able to provide clearer time-frames than I could. We did revamp the whole of the account selector during this milestone, (?3 2025) which is now open and customizable. The Cart and Checkout will be next, but are also in tandem with a lot of revamp we’ll go throughout Catalog.
The current Cart implementation which is really hardly overridable in modern ways (CX, fragment config, business configuration), was actually meant to be fully customized for many of its parts, but still require the good ol’ OSGi integration. Some docs by Roselaine Marques and my original docs (2020 - Liferay only) which don’t account for many pieces of functionality which were added over the years, but still covers the whole of the component architecture and the API to override its parts.
Quite interesting. We have implemented our own account selector because the existing one was not fitting to our needs. The main points where: -) Allow only Accounts where you are a member (admin too, we had to implement our own permissionChecker for that!) -) Allow only Accounts, where the user has a specific permission (we added custom actions + roles) -) MUST show the ERC in the selector -) User can only use specific cart types (based on custom permissions/roles) Obviously most of this had to be implemented in Java and we added our own rest calls for most of the functionality.
Quite interesting. We have implemented our own account selector because the existing one was not fitting to our needs. The main points where: -) Allow only Accounts where you are a member (admin too, we had to implement our own permissionChecker for that!) -) Allow only Accounts, where the user has a specific permission (we added custom actions + roles) -) MUST show the ERC in the selector -) User can only use specific cart types (based on custom permissions/roles) Obviously most of this had to be implemented in Java and we added our own rest calls for most of the functionality.
– Christoph_Rabel