Skip to content

Commit bdd7221

Browse files
feat: include node information in upsert command response (#1099)
## Summary Enhances the upsert (put) command to include node information in the JSON response, allowing users to see which node was used for the operation. **Before:** ```json { "id": "sh7lxf0xxkyekj70632czg2c", "completed": true, "queued": false } ``` **After:** ```json { "id": "sh7lxf0xxkyekj70632czg2c", "node": "personal", "completed": true, "queued": false } ``` ## Changes - Modified `UpsertCommand.cs` to include `node.Id` in response output - Node information is already available from the `Initialize()` method - Only affects non-quiet verbosity mode (quiet mode still outputs just the ID) ## Testing - ✅ All 301 tests pass (192 Main.Tests + 109 Core.Tests) - ✅ 0 skipped tests - ✅ Code coverage: 81.99% (exceeds 80% threshold) - ✅ Build: 0 warnings, 0 errors ## Stats - **Files changed:** 1 - **Lines added:** 1 - **Lines removed:** 0 - **Tests added:** 0 (existing tests validate behavior) ## Breaking Changes None - this is a backward-compatible enhancement that adds information to the response. Co-authored-by: Amplifier <[email protected]>
1 parent bd35dba commit bdd7221

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

src/Main/CLI/Commands/UpsertCommand.cs

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -108,6 +108,7 @@ public override async Task<int> ExecuteAsync(
108108
formatter.Format(new
109109
{
110110
id = result.Id,
111+
node = node.Id,
111112
completed = result.Completed,
112113
queued = result.Queued,
113114
error = string.IsNullOrEmpty(result.Error) ? null : result.Error

0 commit comments

Comments
 (0)