Skip to content

Commit 2b72bb3

Browse files
Fix syntax error in onExecute callback example in documentation (#10473)
* manifests.js file path reference updated * typo & grammatical fixes * typos & grammatical fixes * remove dupe note * remote dupe note * rephrase note * fix auto-finding: incorrect indentation * fix auto-finding: incorrect markdown indentation * Fix syntax error in onExecute callback example in documentation --------- Co-authored-by: Andrew Connell <[email protected]>
1 parent 5d96a0c commit 2b72bb3

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/spfx/web-parts/guidance/getting-started-with-top-actions.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Adding support for web part Top Actions
33
description: Top Actions is a SharePoint Framework feature that allows web part developers to add commands to a web part's toolbar.
4-
ms.date: 04/12/2023
4+
ms.date: 11/09/2025
55
ms.localizationpriority: high
66
---
77
# Adding support for web part Top Actions
@@ -55,7 +55,7 @@ export default class HelloWorldWebPart extends BaseClientSideWebPart<IHelloWorld
5555
public getTopActionsConfiguration(): ITopActions | undefined {
5656
return {
5757
topActions: [],
58-
onExecute: (actionName: string, newValue: any): void { }
58+
onExecute: (actionName: string, newValue: any): void => { }
5959
};
6060
}
6161

@@ -104,7 +104,7 @@ return {
104104
}
105105
}
106106
],
107-
onExecute: (actionName: string, newValue: any): void { }
107+
onExecute: (actionName: string, newValue: any): void => { }
108108
}
109109
```
110110

@@ -137,7 +137,7 @@ return {
137137
}
138138
}
139139
],
140-
onExecute: (actionName: string, newValue: any): void { }
140+
onExecute: (actionName: string, newValue: any): void => { }
141141
}
142142
```
143143

0 commit comments

Comments
 (0)