eject-and-customize

To modify Open Mercato core modules when extensions fall short, you safely eject the required module into your project for direct alteration. This process involves pre-ejection analysis to identify safe modification zones before copying and customizing the core logic.

You need to eject a core module when UMES extensions cannot handle the required depth of changes. Ejection is necessary for scenarios involving schema changes, core business logic alteration, or modification of built-in form elements.

The safest way to alter core business logic is to distinguish between safe and dangerous modification zones after ejecting. You must carefully track all customizations to ensure modifications remain manageable and do not break critical system functions.

To merge upstream changes into customized Open Mercato modules, you apply specific upgrade strategies designed for ejected modules. This ensures your local customizations are preserved while integrating necessary core updates from the platform.

Yes, you can safely change the database schema by ejecting and customizing core modules. The ejection process enables deep structural modifications like schema changes that are impossible through standard UMES extension points.

Before ejecting a core Open Mercato module, you should analyze the specific code boundaries to identify safe and dangerous modification zones. This pre-ejection analysis ensures your customizations remain structurally isolated and manageable.