sf-decomposer 6.15.0 → 6.15.1

package/CHANGELOG.md

@@ -5,6 +5,13 @@
 
 All notable changes to this project will be documented in this file. See [standard-version](https://github.com/conventional-changelog/standard-version) for commit guidelines.
 
+## [6.15.1](https://github.com/mcarvin8/sf-decomposer/compare/v6.15.0...v6.15.1) (2026-05-01)
+
+
+### Bug Fixes
+
+* **deps:** bump config-disassembler to 1.1.2 and harden perf suite ([#423](https://github.com/mcarvin8/sf-decomposer/issues/423)) ([a4aefe6](https://github.com/mcarvin8/sf-decomposer/commit/a4aefe64a3a2458d3cabfd23835c27045ac85941))
+
 ## [6.15.0](https://github.com/mcarvin8/sf-decomposer/compare/v6.14.0...v6.15.0) (2026-04-30)
 
 

package/README.md

@@ -59,6 +59,8 @@ A Salesforce CLI plugin that **decomposes** large metadata XML files into smalle
    sf decomposer decompose -m "flow" -m "labels" --postpurge
    ```
 
+> Combine steps 2 & 3 by configuring the [hooks](#hooks). 
+
 4. **Add decomposed paths to [.forceignore](#forceignore)**  
    This is **required** so the Salesforce CLI does not treat decomposed files as source. Use the [sample .forceignore](https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/examples/.forceignore) and adjust extensions for your chosen format (`.xml`, `.json`, `.yaml`, etc.).
 
@@ -78,6 +80,8 @@ A Salesforce CLI plugin that **decomposes** large metadata XML files into smalle
    sf project deploy start -x "manifest/package.xml"
    ```
 
+   Or run the deploy command directly after configuring the [hooks](#hooks) to run the recompose automatically before deploying.
+
 ---
 
 ## Requirements
@@ -283,17 +287,57 @@ sf project deploy start -x "manifest/package.xml"
 
 **Permission set – unique-id**
 
-![Unique ID](https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/.github/images/decomposed-uid.png)
+```
+permissionsets/
+└── HR_Admin/
+    ├── HR_Admin.permissionset-meta.xml             ← leaf properties (label, description, userLicense, ...)
+    ├── .key_order.json                             ← preserves original element order
+    ├── applicationVisibilities/
+    │   └── JobApps__Recruiting.applicationVisibilities-meta.xml
+    ├── classAccesses/
+    │   └── Send_Email_Confirmation.classAccesses-meta.xml
+    ├── fieldPermissions/
+    │   ├── Job_Request__c.SalaryPay__c.fieldPermissions-meta.xml
+    │   └── Job_Request__c.Salary__c.fieldPermissions-meta.xml
+    ├── objectPermissions/
+    │   └── Job_Request__c.objectPermissions-meta.xml
+    ├── pageAccesses/
+    │   └── Job_Request_Web_Form.pageAccesses-meta.xml
+    ├── recordTypeVisibilities/
+    │   └── Recruiting.DevManager.recordTypeVisibilities-meta.xml
+    ├── tabSettings/
+    │   └── Job_Request__c.tabSettings-meta.xml
+    └── userPermissions/
+        └── APIEnabled.userPermissions-meta.xml
+```
 
 **Permission set – grouped-by-tag**
 
-![Grouped By Tag](https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/.github/images/decomposed-tags.png)
+```
+permissionsets/
+└── HR_Admin/
+    ├── HR_Admin.permissionset-meta.xml             ← leaf properties only
+    ├── .key_order.json
+    ├── applicationVisibilities.xml                 ← all applicationVisibilities entries
+    ├── classAccesses.xml                           ← all classAccesses entries
+    ├── fieldPermissions.xml                        ← all fieldPermissions entries
+    ├── objectPermissions.xml
+    ├── pageAccesses.xml
+    ├── recordTypeVisibilities.xml
+    ├── tabSettings.xml
+    └── userPermissions.xml
+```
 
 ### Custom Labels Decomposition
 
 Custom labels use only the **unique-id** strategy. If you pass `grouped-by-tag`, the plugin overrides to `unique-id` and continues. Grouping labels by tag would produce no difference from the original file since all elements share the same tag. Each label is written to its own file.
 
-![Decomposed Custom Labels](https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/.github/images/decomposed-labels.png)
+```
+labels/
+├── CustomLabels.labels-meta.xml                    ← original wrapper kept (empty after decompose)
+├── quoteAuto.label-meta.xml                        ← one file per <labels> entry, named by fullName
+└── quoteManual.label-meta.xml
+```
 
 ### Additional Permission Set Decomposition
 
@@ -309,7 +353,22 @@ sf decomposer decompose -m "permissionset" -s "grouped-by-tag" -p
 sf decomposer decompose -m "mutingpermissionset" -s "grouped-by-tag" -p
 ```
 
-![Decomposed Perm Set](https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/.github/images/additional-perm-set-decomposed.png)
+```
+permissionsets/
+└── HR_Admin/
+    ├── HR_Admin.permissionset-meta.xml             ← leaf properties
+    ├── .key_order.json
+    ├── applicationVisibilities.xml                 ← grouped-by-tag stays grouped
+    ├── classAccesses.xml
+    ├── pageAccesses.xml
+    ├── recordTypeVisibilities.xml
+    ├── tabSettings.xml
+    ├── userPermissions.xml
+    ├── fieldPermissions/                           ← grouped per object (decompose-nested-permissions)
+    │   └── Job_Request__c.fieldPermissions-meta.xml
+    └── objectPermissions/                          ← one file per object
+        └── Job_Request__c.objectPermissions-meta.xml
+```
 
 ### Loyalty Program Setup Decomposition
 
@@ -320,7 +379,30 @@ sf decomposer decompose -m "mutingpermissionset" -s "grouped-by-tag" -p
 
 > Recomposition for loyalty program setup removes decomposed files even without `--postpurge`. Use version control or CI to keep them if needed.
 
-![Decomposed Loyalty Program Setup](https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/.github/images/decomposed-loyalty-program.png)
+```
+loyaltyProgramSetups/
+└── Cloud_Kicks_Inner_Circle/
+    ├── Cloud_Kicks_Inner_Circle.loyaltyProgramSetup-meta.xml   ← leaf properties (e.g. label)
+    ├── .key_order.json
+    ├── .multi_level.json                                       ← required for recompose; do not hand-edit
+    └── programProcesses/                                       ← one folder per process, named by processName
+        ├── Manual Points Adjustments/
+        │   ├── Manual Points Adjustments.xml                   ← process leaf properties
+        │   ├── .key_order.json
+        │   ├── parameters/                                     ← one file per parameter, named by parameterName
+        │   │   ├── EA_PerAdjustmentRewardTracking.parameters-meta.xml
+        │   │   ├── EventType.parameters-meta.xml
+        │   │   └── ...
+        │   └── rules/                                          ← one file per rule, named by ruleName
+        │       ├── Bulk Voucher Upload.rules-meta.xml
+        │       ├── Finalize.rules-meta.xml
+        │       └── Set Up Step.rules-meta.xml
+        ├── Member Enrollment Process/
+        │   └── ...                                             ← same shape per process
+        └── ...
+```
+
+> **Tip:** This three-level layout (`programProcesses` → `parameters`/`rules`) is exactly the multi-level decomposition pattern. The same pattern powers Bots, Flexipages, and Layouts via opt-in `multiLevel` overrides — see the [admin handbook](https://github.com/mcarvin8/sf-decomposer/blob/main/HANDBOOK.md) for those recipes.
 
 ---
 

package/oclif.manifest.json

@@ -342,5 +342,5 @@
       ]
     }
   },
-  "version": "6.15.0"
+  "version": "6.15.1"
 }

package/package.json

@@ -1,13 +1,13 @@
 {
   "name": "sf-decomposer",
   "description": "Split large Salesforce metadata files into version-control-friendly pieces and rebuild deployment-ready files.",
-  "version": "6.15.0",
+  "version": "6.15.1",
   "dependencies": {
     "@oclif/core": "^4",
     "@salesforce/core": "^8.26.3",
     "@salesforce/sf-plugins-core": "^12.2.6",
     "@salesforce/source-deploy-retrieve": "^12.35.0",
-    "config-disassembler": "^1.1.1",
+    "config-disassembler": "^1.1.2",
     "fast-xml-parser": "^5.7.2",
     "p-limit": "^7.3.0"
   },
@@ -93,6 +93,8 @@
     "test": "wireit",
     "test:nuts": "oclif manifest && vitest run --config ./vitest.nut.config.ts",
     "test:only": "wireit",
+    "test:perf": "vitest run --config ./vitest.perf.config.ts",
+    "test:perf:gen": "node --import ts-node/esm scripts/gen-perf-fixtures.ts",
     "version": "oclif readme"
   },
   "publishConfig": {