Allow optional variables?

[tmeasday]

If I declare a variable type to be nullable (e.g. query people(cursor: Int) { .. } as opposed to Int!), I don't think we should throw an invariant error if the cursor variable is missing.

[jbaxleyiii]

@tmeasday this is a great point! I'll get that fixed and out!

[jbaxleyiii]

@tmeasday I don't think AC allows this?

Error: The inline argument "first" is expected as a variable but was not provided.
      at valueToObjectRepresentation (/Users/james.baxley/Products/apollo/react-apollo/node_modules/apollo-client/data/storeUtils.js:34:19)

[jbaxleyiii]

We could pass null as the value though if they are missing.

[jbaxleyiii]

fixed in #200 (going out today!)

[jbaxleyiii]

should be out soon! https://github.com/apollostack/react-apollo/releases/tag/v0.5.2

[tmeasday]

Do you think we should fix this in AC? Maybe AC can be more strict and force you to explicit about your nulls? I'm not sure.

[jbaxleyiii]

@tmeasday there is an issue open in AC about it where @stubailo was on the fence. I'm happy to do that or keep this shim 🎉

[nicolo-paganin]

@jbaxleyiii the fixing is not working for me. I have react-apollo v0.6 but it is returning me the same error also if the variable is optional

Error: The inline argument "first" is expected as a variable but was not provided.

[tmeasday]

@imthehell perhaps we can open a new issue about this with a reproduction? #200 included a test for this so there must a subtlety in your use case that the test isn't covering.