You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
See docs/TESTING.md for proper testing patterns.`);return mJe}function Ir(){if(process.env.VITEST==="true")throw new Error(`\u{1F6A8} REAL FILESYSTEM EXECUTOR DETECTED IN TEST! \u{1F6A8}
44
+
See docs/dev/TESTING.md for proper testing patterns.`);return mJe}function Ir(){if(process.env.VITEST==="true")throw new Error(`\u{1F6A8} REAL FILESYSTEM EXECUTOR DETECTED IN TEST! \u{1F6A8}
45
45
This test is trying to use the default filesystem executor instead of a mock.
46
46
Fix: Pass createMockFileSystemExecutor() as the fileSystemExecutor parameter in your test.
- ✅ **Universal Compatibility**: Works on any system via npx
106
106
107
-
For complete documentation, examples, and troubleshooting, see @docs/RELOADEROO.md
107
+
For complete documentation, examples, and troubleshooting, see @docs/dev/RELOADEROO.md
108
108
109
109
## Architecture Overview
110
110
@@ -116,13 +116,13 @@ XcodeBuildMCP uses the concept of configuration by convention for MCP exposing a
116
116
117
117
Tools are the core of the MCP server and are the primary way to interact with the server. They are organized into directories by their functionality and are automatically loaded and exposed to MCP clients.
118
118
119
-
For more information see @docs/PLUGIN_DEVELOPMENT.md
119
+
For more information see @docs/dev/PLUGIN_DEVELOPMENT.md
120
120
121
121
#### Resources
122
122
123
123
Resources are the secondary way to interact with the server. They are used to provide data to tools and are organized into directories by their functionality and are automatically loaded and exposed to MCP clients.
124
124
125
-
For more information see @docs/PLUGIN_DEVELOPMENT.md
125
+
For more information see @docs/dev/PLUGIN_DEVELOPMENT.md
126
126
127
127
### Tool Registration
128
128
@@ -141,7 +141,7 @@ XcodeBuildMCP loads tools at startup. To limit the toolset, set `XCODEBUILDMCP_E
For more information see @docs/dev/ARCHITECTURE.md
145
145
146
146
## Testing
147
147
@@ -155,7 +155,7 @@ The project enforces a strict **Dependency Injection (DI)** testing philosophy.
155
155
156
156
This approach ensures that tests are robust, easy to maintain, and verify the actual integration between components without being tightly coupled to implementation details.
157
157
158
-
For complete guidelines, refer to @docs/TESTING.md.
158
+
For complete guidelines, refer to @docs/dev/TESTING.md.
159
159
160
160
## TypeScript Import Standards
161
161
@@ -189,7 +189,7 @@ This ensures all new code follows the `.ts` import pattern and maintains compati
189
189
190
190
Follow standardized development workflow with feature branches, structured pull requests, and linear commit history. **Never push to main directly or force push without permission.**
191
191
192
-
For complete guidelines, refer to @docs/RELEASE_PROCESS.md
192
+
For complete guidelines, refer to @docs/dev/RELEASE_PROCESS.md
0 commit comments