sf-decomposer 5.3.8 → 5.3.9

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.
 
+## [5.3.9](https://github.com/mcarvin8/sf-decomposer/compare/v5.3.8...v5.3.9) (2025-02-10)
+
+
+### Bug Fixes
+
+* **deps:** bump @salesforce/source-deploy-retrieve ([a4aa797](https://github.com/mcarvin8/sf-decomposer/commit/a4aa797cb9b581ebe24950f08c631f75bbbc070e))
+
 ## [5.3.8](https://github.com/mcarvin8/sf-decomposer/compare/v5.3.7...v5.3.8) (2025-02-03)
 
 

package/README.md

@@ -19,6 +19,7 @@
 - [Ignore Files](#ignore-files)
   - [`.forceignore` updates](#.forceignore-updates)
   - [`.gitignore` updates](#.gitignore-updates)
+- [Contributing](#contributing)
 - [Issues](#issues)
 - [License](#license)
 </details>
@@ -46,6 +47,7 @@ Why should you consider using this Salesforce CLI Plugin over Salesforce's decom
 - Salesforce's decomposition is all or nothing for each metadata type. Meaning, if you want to decompose workflows, all of your workflows will need to be decomposed to work with Salesforce's approach. My plugin allows you to selectively decompose for each metadata type.
   - See [Ignore Files when Decomposing](#ignore-files-when-decomposing)
 - Some metadata types may only be partially decomposed by Salesforce such as permission sets based on what designs are picked. My plugin will allow for total decomposition. So if a user wants to fully decompose permission sets, they can use this plugin.
+- When this plugin recomposes the decomposed files, it will sort the elements consistently compared to native Salesforce files.
 
 ## Commands
 
@@ -56,7 +58,14 @@ The `sf-decomposer` supports 2 commands:
 
 ## `sf decomposer decompose`
 
-Decomposes the original metadata files in all local package directories into smaller files for version control. If unique ID elements are found, the decomposed files will be named using them. Otherwise, the decomposed files will be named with the SHA-256 hash of the element contents.
+Decomposes the original metadata files in all local package directories into smaller files for version control. 
+
+When the files are decomposed, it will:
+- decompose leaf elements (i.e. `<userLicense>Salesforce</userLicense>`) in the same file. The leaf file-name will match the original file-name, just in a decomposed directory.
+- decompose nested elements into their own files.
+  - If unique ID elements are found, the decomposed files will be named using them.
+  - Otherwise, the decomposed files will be named with the SHA-256 hash of the element contents.
+  - See [Contributing](#contributing) for more information on unique ID elements.
 
 <img src="https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/.github/images/decomposed-perm-set.png">
 <p><em>Decomposed Permission Sets named using unique ID elements</em></p>
@@ -249,6 +258,10 @@ Optionally, Git (or whatever version control system you are using) can ignore th
 
 You can use the sample [.gitignore](https://raw.githubusercontent.com/mcarvin8/sf-decomposer/main/samples/.gitignore) provided.
 
+## Contributing
+
+Contributions are welcome! See [Contributing](https://github.com/mcarvin8/sf-decomposer/blob/main/CONTRIBUTING.md).
+
 ## Issues
 
 If you encounter any issues, please create an issue in the repository's [issue tracker](https://github.com/mcarvin8/sf-decomposer/issues). Please also create issues for feature enhancements or to support newer metadata types added to the [SDR toolkit](https://github.com/forcedotcom/source-deploy-retrieve).

package/oclif.lock

@@ -1596,10 +1596,10 @@
     string-width "^7.2.0"
     terminal-link "^3.0.0"
 
-"@salesforce/source-deploy-retrieve@^12.14.2":
-  version "12.14.2"
-  resolved "https://registry.yarnpkg.com/@salesforce/source-deploy-retrieve/-/source-deploy-retrieve-12.14.2.tgz#c14c62f2d72d5415265401068bb0e046a2b0f973"
-  integrity sha512-ZLV5YYNZV7d+ONzrgA+VeMsdWr+sqx2WQaswFK6RzrHPqItsczp6RM298oOZm8ZvKJCdQpjiRi0/cDqKGX/nkw==
+"@salesforce/source-deploy-retrieve@^12.14.6":
+  version "12.14.6"
+  resolved "https://registry.yarnpkg.com/@salesforce/source-deploy-retrieve/-/source-deploy-retrieve-12.14.6.tgz#19fee9916619cac38d4b703de3ad9eba10343143"
+  integrity sha512-7a9tzVmRhuja1w05zhW/UpoViA5xYXJGsZlSjAqOPHH5n4e2/q9Q+XeOb2kfusOr34oEHoU+YFcsZXWc9hu0SA==
   dependencies:
     "@salesforce/core" "^8.8.2"
     "@salesforce/kit" "^3.2.3"

package/oclif.manifest.json

@@ -198,5 +198,5 @@
       ]
     }
   },
-  "version": "5.3.8"
+  "version": "5.3.9"
 }

package/package.json

@@ -1,12 +1,12 @@
 {
   "name": "sf-decomposer",
   "description": "Decomposes Salesforce metadata into more manageable files.",
-  "version": "5.3.8",
+  "version": "5.3.9",
   "dependencies": {
     "@oclif/core": "^4",
     "@salesforce/core": "^8.2.1",
     "@salesforce/sf-plugins-core": "^11.2.1",
-    "@salesforce/source-deploy-retrieve": "^12.14.2",
+    "@salesforce/source-deploy-retrieve": "^12.14.6",
     "fs-extra": "^11.2.0",
     "xml-disassembler": "^1.3.11",
     "xml2json-disassembler": "^1.1.11",