fix(test): repair main build — health spec timestamp (post #86/#93 merge)#102
Merged
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.
Main's build broke after merging #86 and #93. Both edited
health.service.spec.ts; they auto-merged textually with no conflict markers, but the result is type-broken — #86 madecheckDatabase's return type requiretimestamp, while the surviving line-66 mock omits it (TS2345,nest buildfails).One-line fix: add
timestampto the mock. Verified locally: build exit 0, full suite 317/317 pass.This is a semantic merge collision (each PR green alone, red combined) — following up by adding
build && testre-verification on post-merge main to the merge process.