We can’t believe that it is already August! Let’s check out the work we did in July:
- HasManyThrough Relation
- Documentation Enhancements
- Reorganize Code and Docs Along Abstraction Levels
- Bug Fixes
- Community Contribution
Since the beginning of the LoopBack project, we have been using the Contributor License Agreement (CLA) as the contribution method. Contributors need to sign each CLA for each LoopBack repository they’re contributing. To simplify the contribution process and encourage community contributions, we are planning to gradually switch to use Developer Certificate of Origin (DCO) as the contribution method.
Welcome back to the “Community Q&A Monthly Digest”, in which we highlight some of the questions and answers in our LoopBack Slack community here.
Over the recent months, this global pandemic has affected our lives in different ways; we hope you all stay safe during these difficult times. The LoopBack team has adapted to new ways of working, including virtually and in new settings. Even though it could be challenging sometimes, we are glad that we were able to complete most of our Q2 plan. Thanks to all the support from the team and the community!
Here’s a brief look at the Q2 summary:
- Migration Guide
- Enhancing Documentation
- Leveraging Authentication System
- APIC/LB4 Integration
- Other Highlights
- Building LoopBack Community
Documentation restructuring, TypeORM support, and HasManyThrough were the three main accomplishments in the month of June. Based on the community feedback, documentation improvement remains our number one priority in the coming month. Besides, while welcoming Nathan Chen join as a maintainer of the
strong-globalize repo, we said farewell to Deepak.
Here is what we did in the month June: