All Projects → amitastreait → Salesforce-Short-Hands

amitastreait / Salesforce-Short-Hands

Licence: other
The main purpose of this repository is to put all the utilities in one place so that other developers can get help and they can also contribute to this repo.

Programming Languages

Apex
172 projects
javascript
184084 projects - #8 most used programming language
HTML
75241 projects

Projects that are alternatives of or similar to Salesforce-Short-Hands

lwc-redux
Integrate Redux with Lightning Web Component
Stars: ✭ 35 (+12.9%)
Mutual labels:  salesforce, salesforce-lightning, salesforce-developers
HTTPCalloutFramework
HTTP Callout Framework - A light weight callout framework for apex HTTP callouts in Salesforce
Stars: ✭ 43 (+38.71%)
Mutual labels:  salesforce, salesforce-developers, salesforce-api
ssjs-lib
An open-source library that takes the repetitive and complex tasks and simplifies them, enabling you to get the most out of Salesforce Marketing Cloud.
Stars: ✭ 28 (-9.68%)
Mutual labels:  salesforce, salesforce-developers, salesforce-api
spaghetti-cmd-loader
Salesforce Custom Metadata Type Loader, designed for Lightning Experience
Stars: ✭ 13 (-58.06%)
Mutual labels:  salesforce, salesforce-lightning, salesforce-developers
apex-fp
Functional programming for Salesforce Apex
Stars: ✭ 231 (+645.16%)
Mutual labels:  salesforce, salesforce-developers, salesforce-api
Salesforce-Custom-Path-Assistant-LWC
A Salesforce custom path assistant built using only Lightning Web Components
Stars: ✭ 37 (+19.35%)
Mutual labels:  salesforce, salesforce-lightning
SimpleLightningComponents
A collection of custom Salesforce Lightning components to try to make Lightning development a little bit less frustrating
Stars: ✭ 37 (+19.35%)
Mutual labels:  salesforce-lightning, salesforce-developers
canvas-starter-kit
A template for developing on the Salesforce Canvas platform in Javascript.
Stars: ✭ 23 (-25.81%)
Mutual labels:  salesforce, salesforce-developers
awesome-lwc
A list of interesting on platform Lightning Web Components resources and code examples
Stars: ✭ 124 (+300%)
Mutual labels:  salesforce, salesforce-developers
R.apex
Functional utility library for Apex
Stars: ✭ 80 (+158.06%)
Mutual labels:  salesforce, salesforce-developers
uswds-sf-lightning-community
A Salesforce Lightning Community Theme and related components built upon US Web Design System
Stars: ✭ 24 (-22.58%)
Mutual labels:  salesforce, salesforce-lightning
apex-mocks-stress-test
Testing out FFLib versus Crud / CrudMock
Stars: ✭ 47 (+51.61%)
Mutual labels:  salesforce, salesforce-developers
apex-rollup
Fast, configurable, elastically scaling custom rollup solution. Apex Invocable action, one-liner Apex trigger/CMDT-driven logic, and scheduled Apex-ready.
Stars: ✭ 133 (+329.03%)
Mutual labels:  salesforce, salesforce-developers
texei-sfdx-plugin
Texeï's plugin for sfdx
Stars: ✭ 99 (+219.35%)
Mutual labels:  salesforce, salesforce-developers
eslint-plugin-aura
Salesforce Lightning (Aura) specific linting rules for ESLint
Stars: ✭ 24 (-22.58%)
Mutual labels:  salesforce, salesforce-lightning
Apex-Code-Conventions
Apex conventions and best practices for Salesforce Developers
Stars: ✭ 28 (-9.68%)
Mutual labels:  salesforce, salesforce-developers
apex-dml-mocking
DML mocking, CRUD mocking, dependency injection framework for Salesforce.com (SFDC) using Apex
Stars: ✭ 38 (+22.58%)
Mutual labels:  salesforce, salesforce-developers
NetCoreForce
Salesforce REST API toolkit for .NET Standard and .NET Core
Stars: ✭ 77 (+148.39%)
Mutual labels:  salesforce, salesforce-api
NebulaFramework
A development framework for Salesforce's Apex language & the Force.com platform
Stars: ✭ 28 (-9.68%)
Mutual labels:  salesforce, salesforce-developers
Script.apex
Evaluate Javascript expressions in Apex
Stars: ✭ 18 (-41.94%)
Mutual labels:  salesforce, salesforce-developers

Salesforce Utils

Validate Against Production Org

Validate Against QA

Enforce branch naming

This repo is maintained by Amit Singh aka SFDCPanther. The main purpose of this repo is to put all the reusable utility which I have developed so that all others can use them. If you wanted to contribute you can also contribute. How to contribute, check the below steps for the same.

Features Uploaded - 11 April 2021

This repository contains the following features

To contribute your utility must qualify below criterias.

  • Utility must be reusable
  • All the Classes, Trigger must have test classes and test classes must cover atleast 85% of your code.
  • Your Utility folder must contain ReadMe.md file with the steps to use the utility. ( If possible create a small video )
  • You must follow the best steps to use your new branch to develop the utility.

Clone the repo to your Local PC.

The very first step is to clone this repo into your salesforce rep. Use the below command. git clone https://github.com/amitastreait/Salesforce-Recepies

Create your own branch in local machine.

Once you have cloned the Repo into your local machine then create a new branch for your utility. The branch name should follow the naming convension like below. If you name is amit singh and utility name is lookup then branch name should be lookup-amit-singh. You can use below command to create your branch. git checkout -b lookup-amit-singh

this will create a new branch and will switch you to your new branch.

Create a Seprate Folder for your Utility

  • Now, the next step is to create a seprate folder and the folder name will say the name of your utility. For example customLookup.
  • To create the folder, go to the folder where you have cloned the project and open it. open sfdxsrc folder and then create a new folder and the folder name should be based on your utility.
  • Your parent Folder will contain the sub folders to store the metadata. For Example, this parent folder will contain the sub folders like. objects, lwc, classes, staticresources, etc.

Folders Path

Modify sfdx-project.json file

Next step is to modify sfdx-project.json file. Open the project in your VS code and then open the file. Add a new path for your new folder. For Example the folder name is customLookup then new path should be

{
   "path": "sfdxsrc/customLookup",
   "default": false
}

Project Path

Push the changes to your branch after utility has been developed

Once you have completed the development of your utility, push the changes to your branch. You can follow the below set of commands to push the changes.

  • stage all the changes using git add . command. Note -- Please make sure you push necessary changes only.
  • Commit all the changes to your local branch using git commit -m "A valid message here that make sense"
  • Push the changes to your branch using git push -u origin yourBranchName. For Example, you branch is lookup-amit-singh then command will be git push -u origin lookup-amit-singh

Create a Pull Request to merge all your changes.

Now, final step from your side is to create a Pull Request from your branch to Master Branch.

Final Review

  • I will review the changes and if everything is ok, I will merge the branch with master branch and you will be notified via email.
  • If there are any issues, I will create an issue and assign it to you.
  • You can resolve that and then again commit your changes. this time you don not need to raise the pull request.
Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].