Migrating existing work to kickasscommerce/framework repository and updating composer.json to reflect the new architecture.
Motivation and context
This allows people to use the framework we build without them being stuck with whatever application layer we decide on. It also separates the framework out into different components allowing easier refactoring and separation of concern.
How has this been tested?
Travis CI
Local installation
Screenshots (if appropriate)
Types of changes
What types of changes does your code introduce? Put an x in all the boxes that apply:
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
Go over all the following points, and put an x in all the boxes that apply.
Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our continuous integration server to make sure your tests and code style pass.
Description
Migrating existing work to
kickasscommerce/frameworkrepository and updatingcomposer.jsonto reflect the new architecture.Motivation and context
This allows people to use the framework we build without them being stuck with whatever application layer we decide on. It also separates the framework out into different components allowing easier refactoring and separation of concern.
How has this been tested?
Screenshots (if appropriate)
Types of changes
What types of changes does your code introduce? Put an
xin all the boxes that apply:Checklist:
Go over all the following points, and put an
xin all the boxes that apply.Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our continuous integration server to make sure your tests and code style pass.
If you're unsure about any of these, don't hesitate to ask. We're here to help!