Skip to content

Commit e9ba77c

Browse files
codeonAtul-Butola
andauthored
Add explicit callout for registering function in function factory (#216)
* Add explicit callout for registering function in function factory * Update functions.mdx --------- Co-authored-by: Atul-Butola <[email protected]>
1 parent 7592a19 commit e9ba77c

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

fern/docs/pages/references/functions.mdx

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,6 +2,7 @@ Using functions, you can provide custom code and link it to your event sources,
22

33
In order to create a snap-in version, functions must be defined as shown in the [code samples](/snapin-development/code-samples). Functions are packaged and provided as an artifact at the time of snap-in version creation and then used to deploy functions to snap-in versions. An artifact may contain multiple function definitions. The artifact is a zip file containing the following files:
44

5+
56
```bash
67
/
78
├── src/
@@ -26,4 +27,9 @@ functions:
2627
- `name`: It is the function name that should match the corresponding function name in the folder.
2728
- `description`: It describes the function.
2829

30+
31+
<Callout intent="note">
32+
Each function should be registered in `src/function-factory.ts` to be available for execution.
33+
</Callout>
34+
2935
Refer to the [function invocation](/snapin-development/references/function-invocation) for details about the exact payload of the function.

0 commit comments

Comments
 (0)