Chris Hendrickson
a25411d4fa
DewConfig in core is now a thin YamlMap wrapper. Feature-specific config classes live in their own packages and expose themselves via Dart extensions: - KanbanConfig, ColumnConfig, TicketTypeConfig + KanbanDewConfig extension moved to packages/kanban/lib/src/kanban_config.dart - McpConfig + McpDewConfig extension added to packages/mcp/lib/src/mcp_config.dart - DewConfig.fromYaml() now trivially wraps the raw YamlMap - All call sites unchanged: context.config.kanban.* / context.config.mcp.* - Added yaml dependency to dew_mcp pubspec - Updated core test to validate raw yaml instead of typed fields - Fixed cross-suite Directory.current isolation (existing issue, not introduced) Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
16 lines
518 B
Dart
16 lines
518 B
Dart
library;
|
|
|
|
export 'src/dew_mcp_base.dart';
|
|
export 'src/mcp_config.dart';
|
|
|
|
import 'package:dew_core/dew_core.dart';
|
|
import 'package:dew_mcp/src/dew_mcp_base.dart';
|
|
|
|
/// Registers the MCP command into [commandRegistry].
|
|
///
|
|
/// Tools are resolved lazily from [commandRegistry.mcpTools] when the server
|
|
/// starts, so all feature packages must call their own [registerCommands]
|
|
/// before this is invoked.
|
|
void registerCommands(CommandRegistry commandRegistry) {
|
|
commandRegistry.register(McpCommand(commandRegistry));
|
|
}
|