Passing along state to Interactive Messages handlers about bolt-js

[mbrevoort]

Hi, thanks :)

Yes, actually the way we've done this is to serialize JSON into the value of the button action.

So we have utility functions like this:

let common = {

    // args takes a JSON stringify'd string and returns an object,
    // fails silently returning an empty object
    unmarshall: (str) => {
      try {
        return JSON.parse(str)
      } catch (ex) {
        console.error(`Error unmarshalling ${str}`, ex)
        return {}
      }
    },

    marshall: JSON.stringify
}

So then your button actions might look something like this:

      actions: [{
        name: 'match_confirmation_yes',
        text: 'Yep, good game.',
        style: 'primary',
        type: 'button',
        value: common.marshall({ id: 'some-id', value: 'yes' })
      },
      {
        name: 'match_confirmation_no',
        text: 'NO WAY ! That\' a lie!',
        type: 'button',
        value: common.marshall({ id: 'some-id', value: 'no' })
      }]

And your action handlers would unmarshall the value and then have an object to deal with:

slapp.action('match_confirmation_callback', 'match_confirmation_yes', (msg, args) => {
  args = common.unmarshall(args)
  // args.id is 'some-id'
  msg.respond('Too bad, maybe next time :wink:!')
});

slapp.action('match_confirmation_callback', 'match_confirmation_no', (msg, args) => {
  args = common.unmarshall(args)
  // args.id is 'some-id'
  msg.respond('What what what ? Someone is trying to cheat then. You need to see this IRL!')
});

[SamirBoulil]

Ok that's a neat trick ! It could be awesome to have the state being handled the same way routes does.

Thank you ;)