Repository navigation
BUG: .$push does not add variables to variable definitions on mutation #175
Description
As you can see in the image above:
The variable is_create_update_xero is not in the variable definitions of updateUser.
Here is the code that I use:
async updateUser () {
await User.fetch({ id: this.authUser.id })
await User.insertOrUpdate({
where: this.authUser.id,
data: {
...this.authUser,
is_email_verified: true
}
})
const user = User
.query()
.where('id', this.authUser.id)
.first()
await user.$push({ is_create_update_xero: false })
}Mutation Type Def
updateUser(
id: ID!,
user: UserInput,
is_create_update_xero: Boolean
): Useraaaaaaaand another weird thing about it is when i do this in another place on the app(authenticated page), it adds the variable definition for is_create_update_xero.
not sure if having an authenticated page changes anything.
Please help :(
Activity
kempsteven commentedon Mar 4, 2021
UPDATE:
There is a bug where if you passed a false/falsy variable on a mutation it will not register the variable definition :coffin_dance:
Example:
that will create a query of
as you can see the
$is_create_update_xero: Boolean!is missing in the variable definition in the query.Without the variable definition, the back end won't be able to receive the
is_create_update_xeroWork around:
I just passed a "false" string: user.$push({ is_create_update_xero: 'false' }) , it looks reallyyy bad
but that's the only workaround I could think of
[-].$push does not add variables to variable definitions on mutation[/-][+]BUG: .$push does not add variables to variable definitions on mutation[/+]