Uh oh!
There was an error while loading. Please reload this page.
fix(runtime): give FormatJson the edit activity kind - #726
Merged
Conversation
#658 added the FormatJson builtin but omitted activityKind and didn't update the builtin-tools semantic-category test expectation, so the 'declares stable semantic categories independently of tool names' test saw FormatJson: undefined and test:dist went red on main. FormatJson reads a file and rewrites it in place (writeFile), same shape as Write/Edit, so 'edit' is the correct category. Sets activityKind: 'edit' on the tool and adds FormatJson: 'edit' to the test expectation.
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
Summary
Give the
FormatJsonbuiltin tool theeditactivity kind, fixing thetest:distfailure onmain.Why
#658 added the
FormatJsonbuiltin but omittedactivityKindand didn't update thebuiltin-toolssemantic-category test expectation. The testdeclares stable semantic categories independently of tool namesthen sawFormatJson: undefinedin thename → activityKindmap and failedtoEqual.test:disthas been red onmainsince (last 3+ CI runs, starting at3127732a).Refs #658.
Scope
Changed:
packages/runtime/src/builtin-tools.ts—FormatJsongetsactivityKind: 'edit'.packages/runtime/src/__tests__/builtin-tools.test.ts— expectation table addsFormatJson: 'edit'.Not included:
grepconfirms no otherFormatJsonassertions across the repo.Verification
npm run -w @maka/runtime test— pass 1228, fail 0 (was failing onbuiltin-tools.test.jsbefore).npm run typecheck— clean across all workspaces.FormatJsonassertions exist outsidebuiltin-tools.test.ts.User-facing impact
None.
activityKinddrives tool-activity grouping in the UI timeline;FormatJsonnow groups withWrite/Edit(it reads + rewrites a file in place) instead of falling through to the unknown bucket. No changelog entry needed (tool added in #658, this only fixes its missing category).Reviewer notes
FormatJsonthe semantic category feat(runtime): rework FormatJson as file-in-place JSON validator #658 should have shipped with — implementation + test expectation in one commit.editis chosen overcommandbecause FormatJson's impl callswriteFileon an existing file, matchingWrite/Edit, notBash(arbitrary command).mainso docs PR docs(frontend): add architecture READMEs for ui, renderer, and desktop #725 (and anything else) can land green.Checklist