Skip to content

When rewriting models, order of rewrites affects resolution of relationships #119

@bajtos

Description

@bajtos

Consider the following three examples of models.json passed to loopback().boot():

// 1. works
AccessToken: {
  options: {
    base: 'AccessToken'
  },
  dataSource: 'db'
},
User: {
  options: {
    base: 'User',
    relations: {
      accessTokens: {
        model: 'AccessToken',
        type: 'hasMany',
        foreignKey: 'userId'
      }
    }
  },
  dataSource: 'db'
},

// 2. does not work, User.prototype.accesTokens is undefined when called from User.login
User: {
  options: {
    base: 'User',
    relations: {
      accessTokens: {
        model: 'AccessToken',
        type: 'hasMany',
        foreignKey: 'userId'
      }
    }
  },
  dataSource: 'db'
},
AccessToken: {
  options: {
    base: 'AccessToken'
  },
  dataSource: 'db'
},

// 3. lowercase name of `accessToken`, it works
User: {
  options: {
    base: 'User',
    relations: {
      accessTokens: {
        model: 'accessToken',
        type: 'hasMany',
        foreignKey: 'userId'
      }
    }
  },
  dataSource: 'db'
},
accessToken: {
  options: {
    base: 'AccessToken'
  },
  dataSource: 'db'
},

I am not sure what is the exact source of the problem, but this does not feel right. It may be a problem of app.boot, in which case juggler should provide an API that app.boot can use to prevent it.

/to @raymondfeng

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions