Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -58,7 +58,6 @@

<ItemGroup>
<PackageReference Include="AWSSDK.DynamoDBv2" Version="3.7.402.2"/>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also drop DDB. Let the MPL define it.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No we should keep DDB here, because DB-ESDK has a direct dependency on DDB.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the world was perfect, I would be 100% on board.
But actually, this library does NOT depend on the DDB, but on the Dafny DDB.
And the Dafny DDB is from the MPL.

But I will not die on this hill.
The hill I will die on is that this dependency resolution is wrong.
It needs to be:

 <PackageReference Include="AWSSDK.DynamoDBv2" Version="[3.7.*, 4.0)" />

OR customers will continue to get confused/runtime exceptions.

<PackageReference Include="AWSSDK.Core" Version="3.7.400.38"/>
<PackageReference Include="DafnyRuntime" Version="$(DafnyVersion)" />
<ProjectReference Include="../../../submodules/MaterialProviders/AwsCryptographicMaterialProviders/runtimes/net/MPL.csproj"/>
<!--
Expand Down
Loading