spree-decorators

You can extend Spree models without forking by using decorators to add associations, validations, scopes, and methods directly to Spree classes. This approach cleanly maintains customizations during framework upgrades without altering the core source code.

A Spree decorator is a mechanism that allows you to modify and extend Spree models and controllers without altering the source code. You need to use one when adding new methods, validations, or prepend hooks to existing Spree classes.

To generate a decorator for a Spree product model, run the command spree generate model_decorator Spree::Product. This creates the necessary file structure to start adding associations, validations, and custom methods to your Spree class.

Yes, you can customize Spree admin controllers without modifying the source code by using decorators. Decorators allow you to prepend hooks and modify existing behavior in controllers while keeping the core Spree structure intact.

The best way to maintain Spree customizations during upgrades is to use decorators instead of forking. Decorators extend functionality by adding methods and validations separately, ensuring overrides are preserved when the core Spree codebase updates.

While decorators extend Spree controllers without forking, they require careful management of prepend hooks and method overrides. Complex structural changes to Spree classes may still conflict with core updates if associations are heavily modified.