fix: add href support to actions in the Toast component

[jashar11]

When passing in actions to a Toast, the href property is not acted upon if the type of the action is ToastActionType.BUTTON. With this fix, the url supplied to href is opened in a new tab when the button is clicked on.

[talkor]

@jashar11 thanks for contributing! When using a link in the Toast it should be provided with the LINK type and not a button.
For example:

const actions = useMemo(() => [{
      type: Toast.actionTypes.LINK,
      text: "Link to action",
      href: "https://google.com"
    }], []);
    return <Toast open actions={actions}>
        General message toast
      </Toast>;
  },

See live example here.
Since it's not a fix I'm closing this PR, if there's any else fix needed please create a new issue. Thanks!

[jashar11]

I think this should still be categorised as a fix because if I simply pass

{
      type: Toast.actionTypes.BUTTON,
      content: "Button text",
      href: "https://google.com"
}

as the actions, I would expect the button click to take me to the external link. If not, then I don't see the point of having a button. At the very least, shouldn't there be an onClick property if a button is provided?

[talkor]

I think this should still be categorised as a fix because if I simply pass

{
      type: Toast.actionTypes.BUTTON,
      content: "Button text",
      href: "https://google.com"
}

as the actions, I would expect the button click to take me to the external link. If not, then I don't see the point of having a button. At the very least, shouldn't there be an onClick property if a button is provided?

It's a UX consideration, if you want to have a button you can use the type: Toast.actionTypes.BUTTON and a Button will be shown, if you want to have a link you can use the type: Toast.actionTypes.LINK and pass the href.

This way the behavior of the Button and Link components is preserved.
Regarding the onClick - you can pass it in the actions object along with type: Toast.actionTypes.BUTTON.