@ds-sfdc/sfparty 1.1.0 → 1.1.1

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.
Files changed (2) hide show
  1. package/README.md +2 -3
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -2,9 +2,9 @@
2
2
 
3
3
  [![NPM](https://img.shields.io/npm/v/@ds-sfdc/sfparty.svg?label=@ds-sfdc/sfparty)](https://www.npmjs.com/package/@ds-sfdc/sfparty) [![Downloads/week](https://img.shields.io/npm/dw/@ds-sfdc/sfparty.svg)](https://npmjs.org/package/@ds-sfdc/sfparty) [![License](https://img.shields.io/badge/License-BSD%203--Clause-brightgreen.svg)](https://github.com/TimPaulaskasDS/sfparty/blob/main/LICENSE.md)
4
4
 
5
- ## Using the template
5
+ ## What is sfparty?
6
6
 
7
- This tool will split Salesforce metadata XML files into YAML parts (or JSON).
7
+ For those that are familiar with Salesforce metadata, you know that it uses large XML files. These XML files are difficult to diff, hard to read, and can cause conflicts and corrupted XML when merging. This tool will split Salesforce metadata XML files into YAML parts (or JSON), and combine them back into XML files. A great solution for your CI/CD needs.
8
8
 
9
9
  ## Install
10
10
 
@@ -27,7 +27,6 @@ sfparty combine
27
27
 
28
28
  ```
29
29
  -n, --name name of metadata file
30
- -a, --all all metadata files of type will be processed
31
30
  -s, --source package directory path specified in sfdx-project.json
32
31
  -t, --target target path to directory to create yaml/json files
33
32
  -h, --help Show help
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@ds-sfdc/sfparty",
3
- "version": "1.1.0",
3
+ "version": "1.1.1",
4
4
  "description": "Salesforce metadata XML splitter for CI/CD",
5
5
  "type": "module",
6
6
  "repository": {