paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 33 Packages Projects Releases Wiki Activity

chore: fixing spelling mistake

Browse Source 
Signed-off-by: blam <ben@blam.sh>
This commit is contained in:
blam
2023-03-17 14:11:11 +01:00
parent 6de23c546f
commit 9adce70834
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/features/software-templates/writing-custom-actions.md
+2 -2
View File
@@ -109,14 +109,14 @@ export const createNewFileAction = () => {
#### A note on naming conventions
Try to keep names consistent for both your own custom actions, and any actions contributed to open source. We've found that a seperation of `:` and using a verb as the last part of the name works well.
Try to keep names consistent for both your own custom actions, and any actions contributed to open source. We've found that a separation of `:` and using a verb as the last part of the name works well.
We follow `provider:entity:verb` or as close to this as possible for our built in actions. For example, `github:actions:create` or `github:repo:create`.
Also feel free to use your company name to namespace them if you prefer too, for example `acme:file:create`.
Prefer to use `camelCase` over `pascalCase` for these actions if possible, which leads to better reading and writing of template entity definitions.
> We're aware that theres some exceptions to this, but try to follow as close as possible. We'll be working on migrating these in the repository over time too.
> We're aware that there are some exceptions to this, but try to follow as close as possible. We'll be working on migrating these in the repository over time too.
### The context object