fix: ensure resolvedAt is updated for legacy claims on transition - #334
Open
Abyy8 wants to merge 1 commit into
Open
fix: ensure resolvedAt is updated for legacy claims on transition#334Abyy8 wants to merge 1 commit into
Abyy8 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #219
Description
This PR fixes an audit invariant failure regarding
resolvedAttimestamps. Legacy claims that were resolved prior to the database migration (and therefore haveresolvedAt = null) were failing to generate a timestamp during subsequent state transitions because the entity assumed the timestamp was already set.Changes Made
claim.entity.tsfor theRESOLVED -> RESOLVEDandRESOLVED -> FINALIZEDtransition paths. This ensures legacy claims receive aresolvedAttimestamp while preserving the original timestamp for newer claims.claim.entity.spec.tsto validate this invariant against legacy data.