speccrew 0.7.1 → 0.7.2
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.
|
@@ -117,8 +117,11 @@
|
|
|
117
117
|
- Root object MUST contain "modules" field (array type)
|
|
118
118
|
- Root object MUST NOT contain "businessModules", "subModules", or "components" fields
|
|
119
119
|
- Each module in "modules" array MUST have exactly two fields: "name" (string) and "entryDirs" (array of strings)
|
|
120
|
-
-
|
|
121
|
-
-
|
|
120
|
+
- Module granularity MUST follow the module_scan.depth configuration from tech-stack-mappings.json
|
|
121
|
+
- When depth=1: first-level subdirectories under module_scan.root are modules (e.g., src/views/system → module "system", src/views/bpm → module "bpm")
|
|
122
|
+
- When depth=2: second-level subdirectories are modules (e.g., src/main/java/com/example/controller → grouped by controller subdirectories)
|
|
123
|
+
- Each module's entryDirs should contain the module root directory path (e.g., ["src/views/system"] for module "system"), NOT individual sub-paths
|
|
124
|
+
- DO NOT flatten hierarchical directories into hyphen-separated sub-modules (e.g., DO NOT create "system-user", "system-role" — create one "system" module instead)
|
|
122
125
|
- Multiple modules MUST NOT share the same entryDirs value. If multiple business areas share the same directory, they belong to ONE module.
|
|
123
126
|
- If the generated JSON does not match this format, you MUST regenerate it before proceeding
|
|
124
127
|
</field>
|