Add a user-data class for generating intercomSettings

[jeobrien]

This adds a UserData class to the Node client, which is exposed through the client like so:

const { UserData } = require('intercom-client');
const settings = {
  verificationSecret: 'abc123',
  app_id: 'xyz789',
  user_id: 1,
  email: 'jess@intercom.io',
  name: 'Jess OBrien',
  company: {
    id: 123,
    name: 'Intercom'
  }
};
const userData = new UserData(settings);
res.send(userData.json());

It returns an escaped json object, including the user_hash required for Identity Verification. You can call window.Intercom(boot) on the client side with the data returned.

[kmiyashiro]

If we're going to delete the secret, we should ensure json can be called multiple times by skipping setUserHash if user_hash is already set in this.settings

[jeobrien]

Updated!

[kmiyashiro]

We might also want to wrap the secret/hash things in a conditional and skip them if this.loggedOut

[jeobrien]

I am skipping the hash already if logged out here: https://github.com/intercom/intercom-node/pull/173/files#diff-4c919967cdaa500e061ab2489c6d0136R38

Do you think we should also skip the verification secret?

[kmiyashiro]

Yeah, it seems like we should skip this work if this.loggedOut || this.settings.user_hash. Since verificationSecret and identifier are only used in setUserHash in json, and getVerificationSecret/getIdentifier are sibling methods, you could move those getters to be called inside setUserHash as well.

[jeobrien]

Great point