I'm still new to Falcor (but i guess everyone is currently) so maybe this is a standard practice that I'm not aware of currently but the issue I noticed was when returning a JSON Graph object from my value server I was just using pathValue to return {path: ['users',0,'name'], value: 'David'} but when using expandCache on my falcor.getCache() I was unable to retrieve the users name it was only returning an object that contains a get function for each letter in the value of the response, But if I viewed the cache of my Falcor model I could see the name of my user.

When looking at index.js:17 I noticed only ref, atom, and error types are supported. After returning to my server code and updating the response to use atom everything started working like a charm.

Not sure what steps to recommend to help others with this problem in the future but considering the Netflix documentation doesn't specify you need to use atom when returning a response maybe we should update the documentation to explain the need for atom or if possibly maybe we can update the expandChild function to support $type not being specified?

I'm happy to submit a PR to help resolve this issue

Hi @ekosz. Thanks for this great little library. I've been using it to integrate falcor with cerebral. I took a cue from your falcor-redux library and implemented a diff and patch strategy with falcor's onChange hook. Basically whenever falcor's cache changes, I diff falcor.getCache with cerebral's single state tree and apply the changes. It's been working surprisingly well.

Unfortunately, when I upgraded to the latest falcor v0.1.15, I noticed there are a bunch of new refs in the falcor cache and I've been getting maximum call size reached when falcor-expand-cache is called.

Looks like the errors starts at index.js on line 31.

Have you run into any problems? If you're unable to reproduce, I'd be happy to create a sample app. Again, thanks for your work here, I hope there's a way forward!