definitely!

do you think automatically removing that field from Algolia index would be a good idea as well?

what about giving a warning when the user removes a field that is part of Algolia? should there be a warning?

either works - though automatically removing it might be more work

perhaps just running the algolia validation on schema change is good

so that the user can see the validation error when they save the schema changes

that might be simpler for you guys to implement

that way if you have other integrations that are dependent on the schema - all those validations can run at that point as well

hi ther

luv graph.cool

it's a good point

hey @puppycodes, awesome to hear that 🎉

Hi there @ianp & @rapzo! 🙌

Does anyone know if there is a way to simulate the Auth0 idTolken in the Graphcool playground? --Thanks

Hey @brad.barnes! We’ll release this feature over the next couple of days. (Maybe even today!)

Perfect timing! Thanks!!!

Could anyone please lend a helping hand (or mind, that is)?

Home.js

import React from 'react'
import { graphql } from 'react-apollo'
import { userContactsQuery } from '../../graphql/queries'
import { modifyUserContacts } from '../../graphql/mutations'
class Home extends React.Component {
   (…)
}
export default graphql(modifyUserContacts)(
	graphql(userContactsQuery, { options: { forceFetch: true } })(Home)
)

mutations.js

import gql from 'graphql-tag'

export const modifyUserContacts = gql`
	mutation ($id: ID!, $firstName: String!, $lastName: String!, $birthDay: Int!, $birthMonth: Int!, $birthYear: Int!) {
		updateUser(
			id: $id,
			firstName: $firstName,
			lastName: $lastName,
			birthDay: $birthDay,
			birthMonth: $birthMonth,
			birthYear: $birthYear) {
				id
				firstName
				lastName
				birthDay
				birthMonth
				birthYear
			}
		updateContacts(
			id: $id
			firstName: $firstName,
			lastName: $lastName,
			birthDay: $birthDay,
			birthMonth: $birthMonth,
			birthYear: $birthYear) {
				id
				firstName
				lastName
				birthDay
				birthMonth
				birthYear
			}
	}
`

The above code only produces

this.props.user

and

this.props.allContacts

as pulled from the

queries.js

file (not listed here). There are no

this.props.updateUser

or

this.props.updateContacts

, though. In other words,

queries

are working, but not the

mutations

.

There is a

this.props.updateQuery

though, with error message:

[Exception: TypeError: 'caller' and 'arguments' are restricted function properties and cannot be accessed in this context. at Function.remoteFunction (<anonymous>:3:14)]

Internal Server Error on File Model, shall contact you on Slack: Request ID: ciyielciq5c750131e4s037e1

Hey @tobias! We’re looking into it. I’ll reach out via DM!

FYI: I've got the same error message as @tobias using Apollo, but I it was because I was not passing an non required argument (

group

, that has a default value), declared in the query:

mutation createUser ($email: String!, $password: String!, $group: String) {
createUser(authProvider: {email: {email: $email, password: $password}}, group: $group) {
    id
    email
    group
  }
}

In Apollo app:

{
  "email": "<mailto:email@email.com|email@email.com>",
  "password": "123"
}

I've it fixed by not declaring it in the query:

mutation createUserWithoutGroup ($email: String!, $password: String!) {
createUser(authProvider: {email: {email: $email, password: $password}}) {
    id
    email
    group
  }
}

as far as I know, Apollo uses

null

for non-required, declared variables that you haven't defined in the

variables

options (or when calling the mutation)

therefore it never even comes to considering the default value

thanks for the heads up @tonietto

Was able to find a solution: missed the

{ name: 'updateUser' }

part.

export default graphql(modifyUserContacts, { name: 'updateUser' })(
	graphql(modifyUserContacts, { name: 'createContact' })(
		graphql(modifyUserContacts, { name: 'updateContact' })(
			graphql(modifyUserContacts, { name: 'deleteContact' })(
				graphql(userContactsQuery, { options: { forceFetch: true } })(Home)
			)
		)
	)
)

Hey all, already mentioned this over intercom but wandering if anyone else is looking for functions for pre-create/update mutations. An example if that doesn't make sense - a user submits to pay for a basket with a special coupon applied and before the order is put through it does some server validation such as ensuring the coupon is valid and that the basket meets the required threshold. Scaphold does it as pre and post custom logic

hey @georgelovegrove 👋 thanks for the feedback! this definitely makes a lot of sense and we're already working on it! we're keeping track of this suggestion here: https://github.com/graphcool/feature-requests/issues/23

@nilan great stuff, would really complete the offering for me with that functionality in 🍻

👋

hi there @ambethia simple smile