{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 闹够了就滚 的问题《Why use IntrospectionFragmentMatcher?》','https://www.manongdao.com/q-1320724.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
Is there any reason to use IntrospectionFragmentMatcher to determine concrete types of values returned from interface and union fields?
I'm talking about apollo-client. I'm using InMemoryCache with addTypename: true, so the type is known the moment the client gets the response.
Meanwhile my console is plagued with warnings like these: 
The only reason I see the documentation hint at is response validation. But why validate the server-sent response at all? If the server is not worth trusting, validation is useless anyway.
The warnings seem to be a bug in apollo. https://github.com/apollographql/apollo-client/issues/3397
If you're using
useQuerythen tryfetchPolicy: 'no-cache'.this solved my issue.