-
-
Notifications
You must be signed in to change notification settings - Fork 724
Tech Doc: OFN Data Model Stock locations
Here we explain how OFN adapts to this entity of Spree's data model.
This is the Spree's 2.0 data model area related to stock locations, tightly related to shipments as well. In v2, Spree adds the notion of location related to stock into the data model.
Although Spree allows creating stock locations we are not ready yet to make us of it as that would mean fitting all the new UI and logic into our existing codebase.
To make OFN work with this part of the database schema we created a single 'default' stock location' per OFN instance, meaning that each OFN database only has one location called default
, with which all shipments will be associated automatically. So we:
- Have only a
default
stock location per instance. - Removed any added UI that may allow users to create/read/update/delete stock locations.
- Provide the required customization on top of Spree so that all shipments use the same stock location.
So this part of the data model looks like this:
Note, highlighted in green, how from OFN we only have a single stock location which will be shared by all shipments in the instance.
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