fix: resolve TypeScript errors in MCP handler tests

- Fix N8nRateLimitError constructor call (takes only retryAfter parameter)
- Fix optional chaining for result.details access
- Mock NodeRepository correctly instead of trying to instantiate it

🤖 Generated with [Claude Code](https://claude.ai/code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
czlonkowski
2025-07-28 18:36:47 +02:00
parent 5cca09d462
commit 48219fb860
3 changed files with 7 additions and 5 deletions

View File

@@ -68,4 +68,6 @@ src/
### Development Workflow Reminders
- When you make changes to MCP server, you need to ask the user to reload it before you test
- When the user asks to review issues, you should use GH CLI to get the issue and all the comments
- When the user asks to review issues, you should use GH CLI to get the issue and all the comments
- When the task can be divided into separated subtasks, you should spawn separate sub-agents to handle them in paralel
- Use the best sub-agent for the task as per their descriptions