Compound foreign key support

[michaelprichardson]

The functionality to be able to string together multiple queries for the foreign key. At the moment there is only one .where(...). Being able to have multiple .where(...).where(...) (Note the firebase limits), would help the queries be more specific.

source: {
    collection: 'master/{someId}/detail',
},
targets: [
    {
        collection: 'details/{someId}/more_detail',
        foreignKey: 'masterId',
        where: [
            {
                field: 'masterId',
                operator: '==',
                value: someId
            },
            {
                field: 'secondId',
                operator: '>',
                value: 0
            },
        ]
    },
],

[nbransby]

Could this not be simplified to

​source: {
    collection: 'users/{userId}/workingCopies',
},
targets: [
    {
        collection: 'changes',
        foreignKey:'workingCopy',
        where: {
           user: '$userId'
        }
    }
],

Do we have a use case for an operator other than ==?

[michaelprichardson]

I have not come across it yet where we need an operator other than ==. I thought about making it optional so that it can easily be changed if we need something else down the line.

So in the above example the where would be constructed as follows:

.where('workingCopy', '==', masterId) // As it has always been
.where('user', '==', userId) // New where

[nbransby]

yep.

Might be worth compiling a list of all the relationship rules we need before implementing this so we know what functionality we will need