magector 2.16.6 → 2.16.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "magector",
|
|
3
|
-
"version": "2.16.
|
|
3
|
+
"version": "2.16.7",
|
|
4
4
|
"description": "Semantic code search for Magento 2 — index, search, MCP server",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"main": "src/mcp-server.js",
|
|
@@ -33,10 +33,10 @@
|
|
|
33
33
|
"ruvector": "^0.1.96"
|
|
34
34
|
},
|
|
35
35
|
"optionalDependencies": {
|
|
36
|
-
"@magector/cli-darwin-arm64": "2.16.
|
|
37
|
-
"@magector/cli-linux-x64": "2.16.
|
|
38
|
-
"@magector/cli-linux-arm64": "2.16.
|
|
39
|
-
"@magector/cli-win32-x64": "2.16.
|
|
36
|
+
"@magector/cli-darwin-arm64": "2.16.7",
|
|
37
|
+
"@magector/cli-linux-x64": "2.16.7",
|
|
38
|
+
"@magector/cli-linux-arm64": "2.16.7",
|
|
39
|
+
"@magector/cli-win32-x64": "2.16.7"
|
|
40
40
|
},
|
|
41
41
|
"keywords": [
|
|
42
42
|
"magento",
|
|
@@ -38,6 +38,14 @@ This project is indexed with Magector. Use the MCP tools below to search the cod
|
|
|
38
38
|
- Include Magento terms: "plugin for save", "observer for order place"
|
|
39
39
|
- Be specific: "customer address validation before checkout" not just "validation"
|
|
40
40
|
|
|
41
|
+
## Analysis Patterns
|
|
42
|
+
|
|
43
|
+
### Negative match audit
|
|
44
|
+
When \`magento_grep\` finds a bug pattern in only SOME files of a known group (e.g. \`orderRepository->save()\` in 5 of 8 transition handlers), always read the files that DON'T match to understand why they differ. This narrows the fix scope — files with a different code path may not need fixing.
|
|
45
|
+
|
|
46
|
+
### Follow up DI listings with code reads
|
|
47
|
+
When \`magento_trace_dependency\` or \`magento_find_plugin\` returns a list of plugins/preferences, don't stop at the names. Use \`magento_read\` or \`Read\` to inspect the actual implementation of each — the root cause is often in a specific condition inside the plugin code, not in the DI wiring itself.
|
|
48
|
+
|
|
41
49
|
## Re-indexing
|
|
42
50
|
|
|
43
51
|
After significant code changes, re-index:
|
|
@@ -40,6 +40,11 @@ Before reading files manually, ALWAYS use Magector MCP tools to find relevant co
|
|
|
40
40
|
- Include Magento terms: "plugin for save", "observer for order place", "checkout totals collector"
|
|
41
41
|
- Be specific: "customer address validation before checkout" not just "validation"
|
|
42
42
|
|
|
43
|
+
## Analysis Patterns
|
|
44
|
+
|
|
45
|
+
- **Negative match audit:** When \`magento_grep\` finds a bug pattern in only SOME files of a group, always read the non-matching files to understand why they differ. This narrows the fix scope.
|
|
46
|
+
- **Follow up DI listings with code reads:** When \`magento_trace_dependency\` or \`magento_find_plugin\` returns plugin/preference names, always read the actual implementation. The root cause is often in a condition inside the code, not in the DI wiring.
|
|
47
|
+
|
|
43
48
|
## Magento Development Patterns
|
|
44
49
|
|
|
45
50
|
- Always check for existing plugins before modifying core behavior
|