test(app): await missing checks validation - #119
Closed
albert20260301 wants to merge 1 commit into
Closed
albert20260301 wants to merge 1 commit into
albert20260301 wants to merge 1 commit into
Conversation
Contributor
Author
|
@francoischalifour could you review this? I picked you because you authored the affected data-app contract test and own the target branch. CI is pending; the review focus is preserving the awaited rejection assertion while resolving the type-aware lint failure. |
Contributor
Author
|
Closing this now-redundant stacked repair: the current target branch already contains the lint-safe assertion and PR #118 has a fully green required workflow. |
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
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.
Fix the CI-only lint failure in the data-app contract test.
The assertion now awaits and captures the rejection explicitly, matching the prior failure assertion in the same test. No production behavior or public API changes.
Validation: