[MSHOP-187] Move functionality from model classes to service class Created: 29/Jun/15 Updated: 16/Mar/23 Resolved: 16/Mar/23 |
|
| Status: | Closed |
| Project: | Magnolia Shop (closed) |
| Component/s: | None |
| Affects Version/s: | 2.2 |
| Fix Version/s: | 2.3.0 |
| Type: | Improvement | Priority: | Major |
| Reporter: | Will Scheidegger | Assignee: | Will Scheidegger |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: |
| Description |
|
Currently much of the shops functionality is located in the ShopUtil class. However some tasks are handled by the model classes. These should be moved to ShopUtil as well so that we get more independence from the model classes (e.g. for an AngularJS frontend) |
| Comments |
| Comment by Will Scheidegger [ 15/Jul/15 ] |
|
All functionality is now in ShopUtil. Is this the best place? Or should there be a separate "ShoppingCartAccessor" class or something similar? |
| Comment by Adam Jones [ 16/Mar/23 ] |
|
Closing due to project being archived. |