From 5345d2498e64f45e301b6097437c9f11f712daa8 Mon Sep 17 00:00:00 2001 From: Christopher Pezza Date: Thu, 2 Jan 2025 14:22:11 -0500 Subject: [PATCH] chore: prettier fixes --- .github/CODE_OF_CONDUCT.md | 2 +- .github/FUNDING.yml | 2 +- .github/ISSUE_TEMPLATE/bug_report.yml | 4 ++-- .github/ISSUE_TEMPLATE/config.yml | 2 +- .github/ISSUE_TEMPLATE/feature_request.yml | 2 +- .github/PULL_REQUEST_TEMPLATE.md | 2 +- README.md | 8 ++++---- 7 files changed, 11 insertions(+), 11 deletions(-) diff --git a/.github/CODE_OF_CONDUCT.md b/.github/CODE_OF_CONDUCT.md index b0cf9de..5da9795 100644 --- a/.github/CODE_OF_CONDUCT.md +++ b/.github/CODE_OF_CONDUCT.md @@ -71,4 +71,4 @@ This Code of Conduct is adapted from the [Contributor Covenant][homepage], versi available at [http://contributor-covenant.org/version/1/4][version] [homepage]: http://contributor-covenant.org -[version]: http://contributor-covenant.org/version/1/4/ \ No newline at end of file +[version]: http://contributor-covenant.org/version/1/4/ diff --git a/.github/FUNDING.yml b/.github/FUNDING.yml index 54afdda..c245d01 100644 --- a/.github/FUNDING.yml +++ b/.github/FUNDING.yml @@ -1,3 +1,3 @@ github: chiefpansancolt ko_fi: chiefpansancolt -patreon: chiefpansancolt \ No newline at end of file +patreon: chiefpansancolt diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml index f45d49f..a060c3c 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.yml +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -24,7 +24,7 @@ body: label: Version description: What version of our software are you running? options: - - "1.0" + - '1.0' validations: required: true - type: dropdown @@ -50,4 +50,4 @@ body: description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/chiefpansancolt/salesforce-automation-framework/blob/main/CODE_OF_CONDUCT.md) options: - label: I agree to follow this project's Code of Conduct - required: true \ No newline at end of file + required: true diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index e306c89..41594e7 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -8,4 +8,4 @@ contact_links: about: Please ask and answer questions here. - name: GitHub Security Bug Bounty url: https://bounty.github.com/ - about: Please report security vulnerabilities here. \ No newline at end of file + about: Please report security vulnerabilities here. diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml index 9431a1e..3131c68 100644 --- a/.github/ISSUE_TEMPLATE/feature_request.yml +++ b/.github/ISSUE_TEMPLATE/feature_request.yml @@ -23,4 +23,4 @@ body: description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/chiefpansancolt/salesforce-automation-framework/blob/main/CODE_OF_CONDUCT.md) options: - label: I agree to follow this project's Code of Conduct - required: true \ No newline at end of file + required: true diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 77cd234..8fab031 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -29,4 +29,4 @@ Please describe the tests that you ran to verify your changes. Provide instructi - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes -- [ ] Any dependent changes have been merged and published in downstream modules \ No newline at end of file +- [ ] Any dependent changes have been merged and published in downstream modules diff --git a/README.md b/README.md index b7386ca..b1752e0 100644 --- a/README.md +++ b/README.md @@ -55,7 +55,7 @@ The Framework supports the below Trigger Contexts - After Delete - After Undelete -2. Now you can create a Handler for your Trigger todo anything you are looking to do. Be sure to think about a couple things when determining how to breakdown your handlers to not have all your code in 1 Handler class. +2. Now you can create a Handler for your Trigger todo anything you are looking to do. Be sure to think about a couple things when determining how to breakdown your handlers to not have all your code in 1 Handler class. - Breakdown to handle a single related object like `TestObjectAccountHandler` - Breakdown to be sure a Query is not duplicated in multiple Handlers @@ -174,9 +174,9 @@ Supported DML Utilities are: - addDeletes(List) 3. Once the file is created then you can create the Custom Metadata Type records for the Trigger Pipeline and Trigger Handler - 1. Create Trigger Pipline record in Custom Metadata Type Trigger_Pipeline__mdt. Be sure to select and enable all contexts you have a pipeline for. - 2. Now create a Trigger Handler in Custom Metadata Type Trigger_Handler__mdt and again check off all applicable Trigger Contexts to implement for said Handler. - 3. Repeat step 2 for each new handler you are implementing. + 1. Create Trigger Pipline record in Custom Metadata Type Trigger_Pipeline\_\_mdt. Be sure to select and enable all contexts you have a pipeline for. + 2. Now create a Trigger Handler in Custom Metadata Type Trigger_Handler\_\_mdt and again check off all applicable Trigger Contexts to implement for said Handler. + 3. Repeat step 2 for each new handler you are implementing. > [!TIP] > Check out example implementation of a Trigger Framework on the Account object in the [example folder](/example/trigger-pipeline).