nested abstract fragment error if returned type not queried about bramble HOT 5 CLOSED

@benzolium Thanks for the report. I've tried to reproduce it using your test but it seems there is a JSON syntax error in the handler response of serviceC (notice the spurious comma after "id": "1". This is the cause of the invalid character '}' error message.

"value": {
	"_bramble_id": "BAR1",
	"_bramble__typename": "BAR",
	"id": "1",
}

from bramble.

Oh, my bad. Good catch, @nmaquet. I'll try to reproduce the issue properly cause I'm still getting this error in actual gateway.

Maybe I should catch the issue somewhere else. 🤔

from bramble.

No worries. Can you double check that your downstream service returns syntactically correct JSON? If you're templating your JSON or using string builders it's easy to make a make a mistake and have that extra comma.

from bramble.

@benzolium Any update on this issue? We'd be happy to help if you have some steps to reproduce the problem.

from bramble.

@nmaquet sorry, got lost in work.

I've just tried to test query on downstream service only.

In my case downstream service returns this for value:

"value": {}

So it is syntactically correct JSON.

from bramble.