ODataFormatter sends different response content type header depending on the type of the object being serialized. For example, serializing a Product might send "application/atom-xml;odata=entry" and serializing a collection of Products would send "application/atom-xml; odata=feed".
Comments: This is a breaking change but we do think it is important. However, the problem is larger than just the type passed into this method: Much of the formatter system takes in declared types instead of instance types, and if we change the system, we have to change it everywhere.
Comments: This is a breaking change but we do think it is important. However, the problem is larger than just the type passed into this method: Much of the formatter system takes in declared types instead of instance types, and if we change the system, we have to change it everywhere.