LoopBack 4 TodoList Application Tutorial - Add TodoList Repository
Page Contents

One great feature of a related model’s repository is its ability to expose a factory function (a function that returns a newly instantiated object) to return a ‘constrained’ version of the related model’s repository. A factory function is useful because it allows you to create a repository whose operations are limited by the data set that applies to the factory function.

In this section, we’ll build TodoListRepository to have the capability of building a constrained version of TodoRepository.

Create your repository

From inside the project folder, run the lb4 repository command to create a repository for the TodoList model using the db datasource. The db datasource shows up by its class name DbDataSource from the list of available datasources.

lb4 repository
? Please select the datasource DbDatasource
? Select the model(s) you want to generate a repository TodoList
   create src/repositories/todo-list.repository.ts
   update src/repositories/index.ts
? Please select the repository base class DefaultCrudRepository (Legacy juggler

Repository TodoListRepository was created in src/repositories/

From there, we’ll need to make two more additions:

  • define the todos property, which will be used to build a constrained TodoRepository
  • inject TodoRepository instance

Once the property type for todos has been defined, use this.createHasManyRepositoryFactoryFor to assign it a repository constraining factory function. Pass in the name of the relationship (todos) and the Todo repository instance to constrain as the arguments for the function.


import {Getter, inject} from '@loopback/core';
import {
} from '@loopback/repository';
import {Todo, TodoList, TodoListRelations} from '../models';
import {TodoRepository} from './todo.repository';

export class TodoListRepository extends DefaultCrudRepository<
  typeof TodoList.prototype.id,
> {
  public readonly todos: HasManyRepositoryFactory<
    typeof TodoList.prototype.id

    @inject('datasources.db') dataSource: juggler.DataSource,
    protected todoRepositoryGetter: Getter<TodoRepository>,
  ) {
    super(TodoList, dataSource);
    this.todos = this.createHasManyRepositoryFactoryFor(

To get the related Todo objects for each TodoList, we can register the inclusion resolver that comes with the HasManyRepositoryFactory. We need to register this resolver to the repository class, which we can do as follows:


this.todos = this.createHasManyRepositoryFactoryFor(

// Add this line to register the resolver
this.registerInclusionResolver('todos', this.todos.inclusionResolver);

Now when you get a TodoList, a todos property will be included that contains your related Todos, for example:

  "id": 2,
  "title": "My daily chores",
  "todos": [
      "id": 3,
      "title": "play space invaders",
      "desc": "Become the very best!",
      "todoListId": 2

On the other end, the BelongsToAccessor also comes with an inclusion resolver property that we can register on the TodoRepository. So, let’s register this resolver to the TodoRepository similar to how we did it for the TodoListRepository:


this.todoList = this.createBelongsToAccessorFor(

// Add this line to register the resolver
this.registerInclusionResolver('todoList', this.todoList.inclusionResolver);

We’re now ready to expose TodoList and its related Todo API through the controller.

Previous step: Add TodoList model

Last step: Add TodoList controller