Custom Function Signatures #13
Merged
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.
Adds support for more flexible custom function definitions with user-defined parameters.
The
--customFunctionoption now supports function signatures in the following format:EVENT_NAMEis the name of the event you are tracking. It should be a string or a pointer to a string. This is required.PROPERTIESis an object of properties for that event. It should be an object / dictionary. This is optional.For example, if your function has a userId parameter at the beginning, followed by the event name and properties, you would pass in the following:
If your function follows the standard format
yourCustomTrackFunctionName(EVENT_NAME, PROPERTIES), you can simply pass inyourCustomTrackFunctionNameto--customFunctionas a shorthand.Resolves #11