Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The CreationTime property cannot be customized to modify the value #564

Closed
dotnet9 opened this issue Apr 17, 2023 · 6 comments
Closed

The CreationTime property cannot be customized to modify the value #564

dotnet9 opened this issue Apr 17, 2023 · 6 comments
Milestone

Comments

@dotnet9
Copy link

dotnet9 commented Apr 17, 2023

Description

The CreationTime is initialized in AuditAggregateRoot. I wrote the method of modifying the time in the inherited class. The last time to write to the database is not the seed time, but the time when the framework is initialized.

132f50b25ef90c89558286363b50fe1

This is the value that comes up when debugging:

edd17dc49aee74d3b134be92e27daef

The value inserted by the database is not the expected seed data time, but the current system time when the data was created:

bc21c7533ac47dad39c353a619505a7

Reproduction Steps

No response

Expected behavior

Can customize and modify CreationTime

Actual behavior

CreationTime cannot be customized

Known Workarounds

No response

.NET version

.NET 8 Preview 3

MASA Framework version

1.0.0-preview.28

Other information

No response

@zhenlei520
Copy link
Contributor

When the attribute is assigned, it will not be assigned again, this will be fixed in subsequent versions

@zhenlei520 zhenlei520 mentioned this issue Apr 20, 2023
3 tasks
@zhenlei520
Copy link
Contributor

Fixed in #566

@dotnet9
Copy link
Author

dotnet9 commented Apr 20, 2023

I have updated p30, but this issue still exists

Fixed in #566

I have updated p30, but this issue still exists

@zhenlei520
Copy link
Contributor

zhenlei520 commented Apr 21, 2023

I have updated p30, but this issue still exists

Fixed in #566

I have updated p30, but this issue still exists

preview.30 does not fix this issue, it will be resolved in the next version

@zhenlei520 zhenlei520 added this to the 1.0.0-rc.1 milestone Apr 23, 2023
@zhenlei520
Copy link
Contributor

Fixed in 1.0.0-preview.31 @dotnet9

@dotnet9
Copy link
Author

dotnet9 commented Apr 27, 2023

Fixed in 1.0.0-preview.31 @dotnet9

Thanks very much. After upgrade the nuget package, these fields have been updated normally.

@dotnet9 dotnet9 closed this as completed Apr 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants