> one service sending one type when you expect another (we promise we will always send a fully-formed object or plain text, oops we sent a list) How exactly wo

> one service sending one type when you expect another (we promise we will always send a fully-formed object or plain text, oops we sent a list) How exactly would this happen if both the output and input are typed? Are you talking about shared (or not) typedefs across services?