style(jev): apply the formatter CI asks for - #1289
Merged
Merged
Conversation
The branch's only CI failure is `biome check src tests examples` on tests/kernel/jev-composition.test.ts: one import list out of order and object literals the formatter would print differently. Applied with `biome check --write` rather than by hand, so the result is what CI computes rather than what I guessed it wants. biome check across all 729 files: clean. jev-composition.test.ts: 3/3.
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.
#1283's only CI failure is the formatter, not a test:
Applied with
biome check --writerather than by hand, so the result is what CI computes rather than what I guessed it wants.Checked here:
biome check src tests examples→ 729 files, clean.vitest run tests/kernel/jev-composition.test.ts→ 3/3.Part of getting the four Jev PRs green together: tangle-network/tangle-router#532 (unblocks
mainand the deploy), tangle-network/agent-eval#764 (digest re-pin plus the product-integrity judges), and agent-dev-container#7620 still to diagnose.