I've started work on refactoring some of bbr to use Rollup + Babel with a more modular design. Overall this should help everyone out to make it more extensible and easier to maintain in the long run. All work will be done on the next branch, if you are submitting a pull request make sure to branch off next until the release is completed.
Since This library is so tightly coupled in places there will be more extensive refactoring required (for example, the base Relation 'class' is dependent on HasOne and HasMany while both HasOne and HasMany extend and depend on Relation).
Due to the nature of this large of a refactor I'm unsure how collaboration will work out with PRs and merge conflicts. It will take extra coordination.
I've started work on refactoring some of bbr to use Rollup + Babel with a more modular design. Overall this should help everyone out to make it more extensible and easier to maintain in the long run. All work will be done on the
nextbranch, if you are submitting a pull request make sure to branch offnextuntil the release is completed.prepublishnpm script task to run rollupRelationRelationfromHasOneandHasMany(create lookup store for relation types)HasOneHasManyCollectionModelStoreSemaphoreRelationto use base objectStoreto use base objectv0.10.0does to ease transitionSince This library is so tightly coupled in places there will be more extensive refactoring required (for example, the base
Relation'class' is dependent onHasOneandHasManywhile bothHasOneandHasManyextend and depend onRelation).Due to the nature of this large of a refactor I'm unsure how collaboration will work out with PRs and merge conflicts. It will take extra coordination.