Joakim Olsson

Would love to. Not sure really were to begin since I'm not sure what is causing the problem though. Currently looking through the diff between rc.46 and rc.49 to get...

Sure thing. Failing query: ``` curl 'http://localhost:4444/query' \ -H 'Accept-Language: en,sv;q=0.9,en-US;q=0.8' \ -H 'Cache-Control: no-cache' \ -H 'Connection: keep-alive' \ -H 'DNT: 1' \ -H 'Origin: http://localhost:3300' \ -H 'Pragma:...

I noticed this in the diff between rc.46 and rc.49: Could it be that the planning visitor is being used by multiple requests at the same time somehow and the...

Hmmm, no, there is a mutex before that of course. It's iterating until it has tried 100 times without finding the field.

Hmmm, the problem seems to be that when using a fragment spread in Apollo, __typename is automatically included in the query and that messes up the planning. Hope that gives...

It's most definitely the fact that a fragment is present. Just including __typename in the query works correctly.

@jensneuse @devsergiy Added a reproduction test in #837

Or more correct, I just added __typename to an existing test which made it fail with "my" error. 😊

Enabling loads of Planner debug-config it seems to lose __typename when in the ConfigurationVisitor: ``` Initial node suggestions: {"ds":0,"path":"query.hero","typeName":"Query","fieldName":"hero","isRootNode":true, "isSelected": true,"select reason": []} {"ds":0,"path":"query.hero.name","typeName":"Character","fieldName":"name","isRootNode":false, "isSelected": true,"select reason": []} {"ds":0,"path":"query.hero.__typename","typeName":"Character","fieldName":"__typename","isRootNode":false, "isSelected":...

Hmmm, that might be due to the FakePlanner having a PlanningBehavior that doesn't include typename though. If I modify that it seems to be planning correctly. Back to digging again.