Graphqlbundle: Upgrading from 0.12 to 0.13.3 changes behaviour of property access on booleans

[ruudk]

| Q | A
| ---------------- | -----
| Bug report? | yes
| Feature request? |no
| BC Break report? | yes
| RFC? |no
| Version/Branch | v0.13.3

When we upgraded our large GraphQL API we noticed that some boolean fields returned null instead of booleans. Upon investigating we found out that some booleans need a resolve attribute like this:

 valid:
   type: 'Boolean!'
+  resolve: '@=value.isValid()'

I think this is related to the removal of the Symfony PropertyAccess component. That component would not only search for get{$fieldName} but also for is{$fieldName}.

Can this be added back?

[mcg-web]

This will be fix by #720.

[ruudk]

@mcg-web Awesome, I'll close this one and wait for the next release. Thanks for the fast reply ⚡