-
-
Notifications
You must be signed in to change notification settings - Fork 731
Tech Doc: OFN Data Model Single shipment per Order
Luis Ramos edited this page Apr 11, 2019
·
1 revision
This is the Spree's 2.0 data model area related to shipments.
Although Spree enables having multiple shipments per order we are not ready to embrace this new feature and change our app to fully support it.
So to make OFN work with this underlying database schema while not adding any new features we have a single shipment per order and hide the support for multiple ones from the user. To do that we:
- Have only a single shipment per order.
- Hide any added UI that allows users to deal with multiple shipments.
- Provide the required customization on top of Spree to ensure just a shipment is created.
- Make calls to
order.shipping_method
go throughorder.shipments.first.shipping_method
.
So this part of the data model will then look like:
Note, highlighted in green, how from OFN we only allow a shipment per order.
Development environment setup
- Pipeline development process
- Bug severity
- Feature template (epic)
- Internationalisation (i18n)
- Dependency updates
Development
- Developer Guidelines
- The process of review, test, merge and deploy
- Making a great commit
- Making a great pull request
- Code Conventions
- Database migrations
- Testing and Rspec Tips
- Automated Testing Gotchas
- Rubocop
- Angular and OFN
- Feature toggles
- Stimulus and Turbo
Testing
- Testing process
- OFN Testing Documentation (Handbooks)
- Continuous Integration
- Parallelized test suite with knapsack
- Karma
Releasing
Specific features
Data and APIs
Instance-specific configuration
External services
Design