ResponseFactory: Add a response factory to the public API

[j82w]

Pull Request Template

Description

This change refactors and exposes a factory to create the item and feed responses. This allows users to create the responses which is necessary if users want to create a custom wrapper for the container abstraction.

ItemResponse<Book> itemResponse = this.cosmosClient.ResponseFactory.CreateItemResponse<Book>(responseMessage);

public abstract CosmosResponseFactory
internal abstract CosmosResponseFactoryInternal : CosmosResponseFactory
internal sealed CosmosResponseFactoryCore : CosmosResponseFactoryInternal

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

[ealsur]

This uses the default serializer, correct? So users with a custom one would still need to do it on their end.

If it uses the default serializer, can we explain more why would you use this versus just calling the Type APIs? Sounds like it's a very specific scenario.

[anujtoshniwal]

If the ResponseFactory is exposed on CosmosClient, for Encryption we'd need to take in the client also as input apart from the Container. Can we avoid this by either exposing it on Container or else have a reverse traversal mechanism from Container up?