In previous versions we made the TableEntityRepository only expose ITableEntity.
This was inconvenient since it required downcasting the returned entities to DynamicTableEntity in order to access its additional properties and manipulate them.
The new Azure.Data.Tables we depend on has a much simpler API for TableEntity, which replaces the old DynamicTableEntity with a simple ITableEntity implementation that just adds an IDictionary<string, object interface on top.
We should should make our entity-based repository/partition expose this new TableEntity object so it's a more effective and intuitive addition to the raw tables API.
In previous versions we made the
TableEntityRepositoryonly exposeITableEntity.This was inconvenient since it required downcasting the returned entities to
DynamicTableEntityin order to access its additional properties and manipulate them.The new
Azure.Data.Tableswe depend on has a much simpler API forTableEntity, which replaces the oldDynamicTableEntitywith a simpleITableEntityimplementation that just adds anIDictionary<string, objectinterface on top.We should should make our entity-based repository/partition expose this new
TableEntityobject so it's a more effective and intuitive addition to the raw tables API.