Contextual event data in custom code event

[#1]

In the event code for a custom code event, is it possible to pass context data in the trigger function, to be available in the action code, in the same way that extension code can:

trigger({
  swipeAngle: 90 // the value would be the detected angle
});

(from Launch Documentation )

In the action code, this context does not seem to be available - the event object has only $type and $rule.

[#2 · Accepted solution]

Thanks for bringing this up! I can confirm that this data doesn't get passed through currently, but there's no reason we can't support it. I'll put it on our list.

[#3]

This was released yesterday in version 1.4.2 of the Core extension.

[#4]

My birthday is in early January.  Maybe this will be my gift!

Thanks for the update.   I appreciate the care that you give to your work!

-Stew

[#5]

The code is complete for this, but Adobe is going into a blackout period where we won't release new code during the holidays unless there is a critical issue. Because of this, the feature is set to be released in early January.

[#6]

Happy Birthday Stew! looks like the Launch team delivered!

[#7]

How about using a direct call rule, there you can also pass data which then is available with event.detail

[#8]

Wow. I expected that this would work, but I'm seeing the same thing.

My Core > Custom Code is this:

And the Action of the same rule is this :

All I see in the console is :

   Rule "test custom code" fired.

1. {$type: "core.custom-code", $rule: {…}}
   1. $rule:
      1. id: "RL02f3b17f28374cbfa44ec037d130a07c"
      2. name: "test custom code"
      3. __proto__: Object
   2. $type: "core.custom-code"
   3. type: "core.custom-code"
   4. get type: ƒ ()
   5. __proto__: Object

[#9]

Indeed! Best gift ever!

On Wed, Jan 9, 2019 at 10:15 AM Jantzen.Belliston <forums_noreply@adobe.com>

[#10]

Thanks everyone. I'll use direct call as a workaround for now, and look forward to seeing this in future.