Update destination functions - including variable scoping [DOC-1065].md #7512
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| @@ -79,6 +79,12 @@ To change which event type the handler listens to, you can rename it to the name | |||
| > info "" | |||
| > Functions' runtime includes a `fetch()` polyfill using a `node-fetch` package. Check out the [node-fetch documentation](https://www.npmjs.com/package/node-fetch){:target="_blank"} for usage examples. | |||
|
|
|||
| ### Variable scoping | |||
|
|
|||
| When declaring settings variables, make sure to declare them in the function handler rather than globally in your Function. This prevents you leaking the settings values across other function instances. | |||
There was a problem hiding this comment.
Suggested change
| When declaring settings variables, make sure to declare them in the function handler rather than globally in your Function. This prevents you leaking the settings values across other function instances. | |
| When declaring settings variables, declare them in the function handler rather than globally in your function. This prevents you from leaking the settings values across other function instances. |
|
|
||
| When declaring settings variables, make sure to declare them in the function handler rather than globally in your Function. This prevents you leaking the settings values across other function instances. | ||
|
|
||
| The handler for Destination functions is event-specific, for example, `onTrack()`, `onIdentify()`, etc. |
There was a problem hiding this comment.
Suggested change
| The handler for Destination functions is event-specific, for example, `onTrack()`, `onIdentify()`, etc. | |
| The handler for destination functions is event-specific. For example, you might have an `onTrack()`or `onIdentify()` function handler. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Added section on variable scoping
Merge timing
24th March
Related issues
PR 7511