Skip to content
Build

fix: don't use user transaction, but use ef savechanges instead #2014

Sign in to view logs

fix: don't use user transaction, but use ef savechanges instead

fix: don't use user transaction, but use ef savechanges instead #2014

Triggered via pull request June 28, 2024 08:36
@jvandaaljvandaal
synchronize #793
dont-use-transaction
Status Success
Total duration 3m 19s
Artifacts –

build.yml

on: pull_request
Build
3m 9s
Build
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
Build: src/ParcelRegistry/Parcel/Commands/MigrateParcel.cs#L14
'ParcelId' is obsolete: 'This is a legacy valueobject and should not be used anymore.'
Build: src/ParcelRegistry/Parcel/Commands/MigrateParcel.cs#L24
'ParcelId' is obsolete: 'This is a legacy valueobject and should not be used anymore.'
Build: src/ParcelRegistry/Parcel/Commands/MigrateParcel.cs#L26
'ParcelStatus' is obsolete: 'This is a legacy valueobject and should not be used anymore.'
Build: src/ParcelRegistry/Parcel/Parcel.cs#L15
'ParcelId' is obsolete: 'This is a legacy valueobject and should not be used anymore.'
Build: src/ParcelRegistry/Parcel/Events/ParcelWasMigrated.cs#L44
'ParcelId' is obsolete: 'This is a legacy valueobject and should not be used anymore.'
Build: src/ParcelRegistry/Legacy/Parcel.cs#L20
'ParcelStatus' is obsolete: 'This is a legacy valueobject and should not be used anymore.'
Build: src/ParcelRegistry/Legacy/ValueObjects/ParcelStatus.cs#L36
'ParcelStatus' is obsolete: 'This is a legacy valueobject and should not be used anymore.'
Build: src/ParcelRegistry/Legacy/Parcel.cs#L38
'ParcelId' is obsolete: 'This is a legacy valueobject and should not be used anymore.'
Build: src/ParcelRegistry/Legacy/Parcel.cs#L38
'IParcelFactory' is obsolete: 'This is a legacy interface and should not be used anymore.'
Build: src/ParcelRegistry/Legacy/ValueObjects/ParcelStatus.cs#L29
'ParcelStatus' is obsolete: 'This is a legacy valueobject and should not be used anymore.'