Skip to main content

8 min read
Dominique Emond

Originally published on strongloop.com

It's a Leap Year this year, and we continue to make leaps in LoopBack 4.

With New Year's resolutions in mind, we quickly got started on several items.

Check out the sections below for the progress we made in each area:

6 min read
Diana Lau
Agnes Lin

Originally published on strongloop.com

Happy New Year! The number of LoopBack 4 downloads in 2019 increased more than double than that in 2018. Thank you for your continuous support in using and contributing to LoopBack. We cannot do this alone and we really appreciate all the contributions from the community. In December, we were happy to have 3 community members join us as maintainers: @derdeka, dougal83 and achrinza!

As year 2020 commences, let us summarize our development activities in the last quarter of 2019.

11 min read
Agnes Lin

Originally published on strongloop.com

It's 2锔忊儯0锔忊儯2锔忊儯0锔忊儯!

Happy New Year! Is the snow dancing outside of your window or is the sunshine bringing warmth and glow to the grass around you? No matter where you are, the LoopBack team is thankful for you being with us through 2019! It means a lot to us that you choose LoopBack for your applications and projects.

We're also excited to have Denny, Douglas, and Rifa as LoopBack maintainers! They've been actively helpful in our community. We appreciate all the contributions and great work. Welcome to the team!

Even though this past December was a short month due to the holidays, the list of the accomplished tasks is not short! Check out the sections below for the progress we made in each area:

8 min read
Dave Whiteley

Originally published on strongloop.com

As 2019 draws to a close, we're continuing our annual tradition of celebrating the hard work that the LoopBack team achieved in the past year. As you might expect, developing LoopBack 4 was the main focus, with events, updates and "how to" content adding flavour to the mix. That focus has resulted in a lot of improvements and features for the framework, as well as quality interaction with the LoopBack community.

Grab your seasonal beverage of choice, whether hot or cold, and read on for a trip down 2019 memory lane!

9 min read
Janny Hou

Originally published on strongloop.com

The LoopBack team greeted November with the CASCONxEVOKE conference in Toronto. CASCONxEVOKE is one of Canada's largest combined academic, research and developer conferences. As its speakers and attendees, we had a booth with posters to advocate LoopBack, and also delivered a workshop about developing extensible LoopBack applications. You can check this blog for more details.

For Q4 achievements, we finished 3 epics this month: Inclusion of related models, Deployment guide in a cloud native environment and Support partitioned database in Cloudant connector, and significantly progressed in the Migration, Authentication & Authorization epics.

Keep reading to learn about the recently added features!

4 min read
Raymond Feng

Originally published on strongloop.com

When we build APIs and microservices nowadays, we choose a cloud as the target for deployment. Cloud has long gone beyond being just hosting providers. Infrastructures such as Docker and Kubernetes have completely changed the paradigm of how applications work and operate. To unleash the full power of cloud, there are a few important perspectives that require efforts to make your application cloud native. At LoopBack, we kicked off the journey to provide integration and guidance aligned with CNCF to make your API and microservice applications cloud native throughout the life cycle. This blog summarizes what we have explored and achieved so far to illustrate how you can go cloud native with LoopBack 4.

3 min read
Wen Bo

Originally published on strongloop.com

Part 7: Wrap-Up

In This Episode

This is the final episode of this series. We've used LoopBack 4 to build an online web text-based adventure game. We've built the foundation with LoopBack, and I am going to summarize what we have achieved so far, and how can you apply all of this to your own project.

What We Have Achieved

In episode 1, we created a simple APIs. You can do the same to create a start point for your own project, for example, a student registration system which has a student model with properties like studentId, name, major, and course. Then we connected our project to MongoDB. You have the freedom to choose any database you want. LB4 supports most databases very well.

3 min read
Diana Lau

Originally published on strongloop.com

CASCONxEVOKE is one of Canada鈥檚 largest鈥痗ombined academic, research and developer conferences, welcoming 1,500+ attendees and 150+ speakers. This year, the LoopBack team attended and kept busy collaborating with other attendees at the LoopBack booth and delivering a workshop at the conference between November 4th and 6th in Markham Ontario

7 min read
Dominique Emond

Originally published on strongloop.com

As the cold autumn winds and frost nipped at our heels, the LoopBack team kept warm with generous portions of hot tea and coffee and accomplished their planned October milestone goals.

We focused on the following areas:

  • Inclusion of related models
  • Adding Partitioned Database Support for Cloudant and CouchDB connector
  • Spike on Migration Guide
  • Improvements to Shopping Cart Example
  • CASCON x Evoke 2019 Workshop Preparation
  • Repository Tests for PostgreSQL
  • Generating Controller/Repository from a Model
  • Documentation Improvements
  • Bug fixes / CI fixes

See the October milestone for an overview of what we have worked on, and read on for more details.

7 min read
Agnes Lin

Originally published on strongloop.com

LoopBack 4 now offers a new feature: inclusion of related models! This addition not only simplifies querying data in LoopBack 4, but since we have similar features in LoopBack 3 it also closes one feature gap between LoopBack 3 as well. The idea is to use the inclusion resolver, which is a function that helps to query data over different relations, to achieve such simplifications for us.

Here is a simple use case of inclusion: a customer has many orders.

hasMany

If we'd like to get a customer's instance with all their orders instances, we can query on Customer with filter {include: [{relation: 'orders']}. The inclusion resolvers are similar to GraphQL resolvers -- it will find the target instances of Customer first and pass its result to the inclusion resolver of orders. The query result will contain the return value of orders nested under corresponding Customer instead of connecting to database twice. Read on for detailed examples and explanations!