Closed EmanueleMinotto closed 8 years ago
Seems fine and there is already an alternative for WindowsAzureTableStorage
a user can switch to. Will WindowsAzureTableStorage
and its dependent classes removed in a future version of KeyValueStore? Should the KeyValueStore version in that the classes and the interface are removed named inside the deprecation message?
In the first release it will be still included and removed from v2 (https://github.com/doctrine/KeyValueStore/issues/46).
The AzureSdkTableStorage
should be used instead of the WindowsAzureTableStorage
, do you suggest to write it in these annotations too?
I suggest to name the version inside the deprecation messages when they will be removed. In that case v2.
:+1:
These classes are currently used only for the deprecated
WindowsAzureTableStorage
, so imo should be marked as deprecated too.