Generates the Apex trigger *.trigger file and associated metadata file. These files must be contained in a parent directory called “triggers” in your package directory. Either run this command from an existing directory of this name, or use the –output-dir flag to generate one or point to an existing one.
If you don’t specify the –sobject flag, the .trigger file contains the generic placeholder SOBJECT; replace it with the Salesforce object you want to generate a trigger for. If you don’t specify –event, “before insert” is used.
Aliases for template generate apex trigger
force:apex:trigger:create
apex:generate:trigger
Flags
Flag Name (Long)
Flag Name (Short)
Description
‑‑api‑version
N/A
Type: Value
Override the api version used for api requests made by this command
‑‑event
‑e
Type: Value Valid Values:before insert, before update, before delete, after insert, after update, after delete, after undelete Default value:before insert
Events that fire the trigger.
‑‑flags‑dir
N/A
Type: Value
Import flag values from a directory.
‑‑json
N/A
Type: Boolean
Format output as json.
‑‑name
‑n
Type: Value Required
Name of the generated Apex trigger
The name can be up to 40 characters and must start with a letter.
‑‑output‑dir
‑d
Type: Value Default value:.
Directory for saving the created files.
The location can be an absolute path or relative to the current working directory. The default is the current directory.
‑‑sobject
‑s
Type: Value Default value:SOBJECT
Salesforce object to generate a trigger on.
‑‑template
‑t
Type: Value Valid Values:ApexTrigger Default value:ApexTrigger
Template to use for file creation.
Supplied parameter values or default values are filled into a copy of the template.
Examples for template generate apex trigger
Generate two files associated with the MyTrigger Apex trigger (MyTrigger.trigger and MyTrigger.trigger-meta.xml) in the current directory:
j