Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Domains] Move Orders model and controller to Order Management engine #3052

Closed
luisramos0 opened this issue Nov 15, 2018 · 2 comments
Closed

Comments

@luisramos0
Copy link
Contributor

It was discussed in the Porto gathering that this would be the best next step for the evolution of OFN into Domains.
Creating a Domain of a core component of OFN is really what we need to be assured this separation into domains will not cause to much trouble and still delivery its value of breaking OFN business logic into smaller less complex parts.
The chosen domain was the BackOffice Order management (maybe we can call it Order Fulfilment, a very common name for this component in other retail systems). In this issue we should create the new BackOffice domain and move the Spree::Order object decorator, its controller and also the back office order management pages. We can either move a big part of this scope or maybe start we some of the parts, like the Order Edit page.

This work as being discussed in https://community.openfoodnetwork.org/t/breaking-ofn-down-into-domains/1377
It has been documented in https://github.com/openfoodfoundation/openfoodnetwork/wiki/Tech-Doc:-How-OFN-is-organized-in-Domains-using-Rails-Engines
And it has been started in #2521

@luisramos0
Copy link
Contributor Author

We already have a OrderManagement engine with some reports code. This issue now represents the move of the Orders model and controller to the engine.

@sigmundpetersen sigmundpetersen changed the title Break OFN into domains - New Domain: Orders [Domains] Move Orders model and controller to Order Management engine Sep 27, 2022
@lin-d-hop
Copy link
Contributor

CLosing as this is no longer an agreed forthcoming priority.... still might be a good idea :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants