5119cd2d8e
* fix(research, tasks): Make research command and task updates tag-aware * refactor(tasks): Prevent automatic task file generation across other locations This commit refactors several core task management functions to prevent them from automatically regenerating individual task files after modifying the main `tasks.json`. Previously, operations like `add-task`, `clear-subtasks`, `expand-task`, and `update-task-by-id` would immediately trigger `generateTaskFiles`. This could be slow and was often unnecessary. The calls to `generateTaskFiles` have been removed or commented out from the core task functions. Users should now run `task-master generate` explicitly to update their individual task files. Additionally, this commit includes fixes to the `move` command to make it fully tag-aware. * fix: move and clear subtasks mcp commands * chore: fix format * chore: fix unit tests --------- Co-authored-by: Ralph Khreish <35776126+Crunchyman-ralph@users.noreply.github.com>
95 lines
2.5 KiB
JavaScript
95 lines
2.5 KiB
JavaScript
/**
|
|
* tools/clear-subtasks.js
|
|
* Tool for clearing subtasks from parent tasks
|
|
*/
|
|
|
|
import { z } from 'zod';
|
|
import {
|
|
handleApiResult,
|
|
createErrorResponse,
|
|
withNormalizedProjectRoot
|
|
} from './utils.js';
|
|
import { clearSubtasksDirect } from '../core/task-master-core.js';
|
|
import { findTasksPath } from '../core/utils/path-utils.js';
|
|
|
|
/**
|
|
* Register the clearSubtasks tool with the MCP server
|
|
* @param {Object} server - FastMCP server instance
|
|
*/
|
|
export function registerClearSubtasksTool(server) {
|
|
server.addTool({
|
|
name: 'clear_subtasks',
|
|
description: 'Clear subtasks from specified tasks',
|
|
parameters: z
|
|
.object({
|
|
id: z
|
|
.string()
|
|
.optional()
|
|
.describe('Task IDs (comma-separated) to clear subtasks from'),
|
|
all: z.boolean().optional().describe('Clear subtasks from all tasks'),
|
|
file: z
|
|
.string()
|
|
.optional()
|
|
.describe(
|
|
'Absolute path to the tasks file (default: tasks/tasks.json)'
|
|
),
|
|
projectRoot: z
|
|
.string()
|
|
.describe('The directory of the project. Must be an absolute path.'),
|
|
tag: z.string().optional().describe('Tag context to operate on')
|
|
})
|
|
.refine((data) => data.id || data.all, {
|
|
message: "Either 'id' or 'all' parameter must be provided",
|
|
path: ['id', 'all']
|
|
}),
|
|
execute: withNormalizedProjectRoot(async (args, { log, session }) => {
|
|
try {
|
|
log.info(`Clearing subtasks with args: ${JSON.stringify(args)}`);
|
|
|
|
// Use args.projectRoot directly (guaranteed by withNormalizedProjectRoot)
|
|
let tasksJsonPath;
|
|
try {
|
|
tasksJsonPath = findTasksPath(
|
|
{ projectRoot: args.projectRoot, file: args.file },
|
|
log
|
|
);
|
|
} catch (error) {
|
|
log.error(`Error finding tasks.json: ${error.message}`);
|
|
return createErrorResponse(
|
|
`Failed to find tasks.json: ${error.message}`
|
|
);
|
|
}
|
|
|
|
const result = await clearSubtasksDirect(
|
|
{
|
|
tasksJsonPath: tasksJsonPath,
|
|
id: args.id,
|
|
all: args.all,
|
|
projectRoot: args.projectRoot,
|
|
tag: args.tag || 'master'
|
|
},
|
|
log,
|
|
{ session }
|
|
);
|
|
|
|
if (result.success) {
|
|
log.info(`Subtasks cleared successfully: ${result.data.message}`);
|
|
} else {
|
|
log.error(`Failed to clear subtasks: ${result.error.message}`);
|
|
}
|
|
|
|
return handleApiResult(
|
|
result,
|
|
log,
|
|
'Error clearing subtasks',
|
|
undefined,
|
|
args.projectRoot
|
|
);
|
|
} catch (error) {
|
|
log.error(`Error in clearSubtasks tool: ${error.message}`);
|
|
return createErrorResponse(error.message);
|
|
}
|
|
})
|
|
});
|
|
}
|