skuid.events.publish documentation clarification

John, when you say "the second input didn't come through", can you elaborate on that? Are you using "skuid.events.subscribe" to subscribe to the event, and if so, can you share your code that you're using?

When I subscribe like this:

skuid.events.subscribe("acme.page.resize", function(config, eventDetails) {
   console.log(config);
   console.log(eventDetails);
}); 

And then publish like you were doing initially, everything works as I'd expect:

var config = {
    doSomething: true
};
var eventDetails = {
    direction: 'vertical'
}; 
skuid.events.publish('acme.page.resize',[config,eventDetails]);

I get config and eventDetails coming through in the two console logs like I'd expect.

I'm using a declarative action sequence to subscribe to the event, the idea being to kick off an action sequence from a link (i.e. from a url or div in a template), but keep the logic declarative by leveraging the action sequence.  This may be a nuance with how the action sequence handles the subscription or not understanding the full structure of the data array of the event api.

I may not have fully picked up on how this is supposed to work, but what I was seeing is that in the example provided in the documentation, two objects are passed into the data array in the publish API.  The action sequence only picked up the first object as an input parameter.  When I switched this to one object with two key value pairs, the action sequence picked up both.

i.e. change:

config = {
        doSomething: true
};
var eventDetails = {

    direction: 'vertical'
}; 
skuid.events.publish('acme.page.resize',[config,eventDetails]);
to:
config = {
    doSomething: true,
    direction: 'vertical'
}; 
skuid.events.publish('acme.page.resize',[config]);

I figured this might be a minor documentation issue, which took a couple hours to work out, so I thought I would spare others.  Here's a screenshot of the different outputs:


This worked as I would expect:


The action sequence only picks up parameter1: