server/csharp: Fix issues around last_updated
field.
#85
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed?
This PR fixes an issue where the UI would not display timestamps, or appear to visibly update them during ticket resolve/unresolve UI interactions, when using the
csharp
server profile.The cause was the C# server's EF Core model expecting (and serializing) the field as
lastUpdated
instead oflast_updated
. By adding a few model annotations + UTC conversion logic in the controller, things seem to be back in working order.curl /tickets before fix
curl /tickets after fix