cloud/music_library
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

DRAFT-1: fix labels

Browse Source
This commit is contained in:
Claudio Ortolina
2026-05-12 06:00:19 +01:00
parent 0a80f14bc9
commit edd0da5770
1 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
backlog/drafts/draft-1 - Extend-format-on-edit.ts-to-run-on-files-modified-via-Backlog-MCP-tools.md
+4 -4
View File
@@ -3,11 +3,9 @@ id: DRAFT-1
title: Extend format-on-edit.ts to run on files modified via Backlog MCP tools title: Extend format-on-edit.ts to run on files modified via Backlog MCP tools
status: Draft status: Draft
assignee: [] assignee: []
created_date: '2026-05-10 06:59' created_date: "2026-05-10 06:59"
labels: labels:
- pi-extension - pi
- tooling
- backlog
dependencies: [] dependencies: []
references: references:
- .pi/extensions/format-on-edit.ts - .pi/extensions/format-on-edit.ts
@@ -17,7 +15,9 @@ priority: low
## Description ## Description
<!-- SECTION:DESCRIPTION:BEGIN --> <!-- SECTION:DESCRIPTION:BEGIN -->
The pi extension `.pi/extensions/format-on-edit.ts` currently formats files (Elixir via `mix format`, markdown via `prettier`) only when the `edit` or `write` tools are used. When Backlog MCP tools (`backlog_task_edit`, `backlog_document_create`, etc.) modify files under `backlog/`, no formatting is triggered. The pi extension `.pi/extensions/format-on-edit.ts` currently formats files (Elixir via `mix format`, markdown via `prettier`) only when the `edit` or `write` tools are used. When Backlog MCP tools (`backlog_task_edit`, `backlog_document_create`, etc.) modify files under `backlog/`, no formatting is triggered.
The `tool_result` event fires for the `mcp` tool with `event.input.tool` set to the Backlog tool name, so it's technically possible to hook into these calls. The main challenge is mapping MCP tool calls to the specific files that were modified. The `tool_result` event fires for the `mcp` tool with `event.input.tool` set to the Backlog tool name, so it's technically possible to hook into these calls. The main challenge is mapping MCP tool calls to the specific files that were modified.
<!-- SECTION:DESCRIPTION:END --> <!-- SECTION:DESCRIPTION:END -->