You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We currently use TableEntity for out TableEntityRepository. This limits the scenarios where you can use this repository, since it would not allow reading additional properties that may exist in the table, and also would not allow entity merging behavior like #46 introduced.
By switching the public API to ITableEntity, we would remain API-compatible with the previous version, but using DynamicTableEntity implementation internally would allow saving/merging additional properties as needed.
The text was updated successfully, but these errors were encountered:
kzu
changed the title
Switch from TableEntity to DynamicTableEntity in the non-generic repository for flexibility
Switch from TableEntity to ITableEntity in the non-generic repository for flexibility
Jul 1, 2021
kzu
added a commit
that referenced
this issue
Jul 1, 2021
By switching the public API to ITableEntity, we remain API-compatible with the previous version, but using DynamicTableEntity implementation internally allows saving/merging additional properties as needed.
The caller would need to downcast to `DynamicTableEntity` still, but the scenario woiuld be enabled.
Fixes#48
By switching the public API to ITableEntity, we remain API-compatible with the previous version, but using DynamicTableEntity implementation internally allows saving/merging additional properties as needed.
The caller would need to downcast to `DynamicTableEntity` still, but the scenario woiuld be enabled.
Fixes#48
We currently use
TableEntity
for outTableEntityRepository
. This limits the scenarios where you can use this repository, since it would not allow reading additional properties that may exist in the table, and also would not allow entity merging behavior like #46 introduced.By switching the public API to
ITableEntity
, we would remain API-compatible with the previous version, but usingDynamicTableEntity
implementation internally would allow saving/merging additional properties as needed.The text was updated successfully, but these errors were encountered: