Skip to content

Commit 65136cd

Browse files
author
codetoad
committed
added information about calling command.setBasicName()
1 parent 660a95f commit 65136cd

2 files changed

Lines changed: 8 additions & 1 deletion

File tree

docs/command-logging.md

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -21,6 +21,14 @@
2121
!!! important
2222
Commands can not be reused. They can be scheduled multiple times, but they can not have multiple parents.
2323

24+
## Customization
25+
26+
By default, commands will be logged using their class name. Specifically, `class.getSimpleName()`.
27+
28+
If you want to have a command with a different name you can call `command.setBasicName()`.
29+
30+
Reasons for this may be if you have a command that is context dependant and want to easily differentiate between its use cases.
31+
2432
## How Command Logging works
2533

2634
!!! note

docs/subsystem-logging.md

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -182,7 +182,6 @@ Starting off simple, all the `InputProvider` classes do is provide a common inte
182182

183183
### Inputs
184184

185-
<<<<<<< HEAD
186185
Inputs contain the actual fields that are being logged.
187186

188187
Similar to Command Logging, we want to maintain a tree like structure for our Inputs. To do this, each Inputs extends `FolderLoggableInputs` which in turn extends `LoggableInputs`.

0 commit comments

Comments
 (0)