fix(message overrides): extract message content with Platform-Specific Overrides

[buddyeorl]

Description of changes

• Exposed getClientInfo function from @aws-amplify/core
• Refactored the extractContent function to accept a platform argument and use it to extract the correct platform override button actions and links from the message.

Issue #, if available

Issue 12915

Description of how you validated changes

• Set up pinpoint in app messages with android, and ios and web overrides
• Used Verdaccio to install updated packages on test apps, react native android, ios and react app.
• Confirmed that overrides where extracted correctly and the button actions triggered the correct event.
• Repeated the steps setting up pinpoint in app messages, with no overrides and with only single platform overrides.

Checklist

• PR description included
• yarn test passes
• Tests are changed or added

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[Samaritan1011001]

@buddyeorl, appreciate this very much. I added a few questions and suggestions. Looking forward to work with you to get this in.

[Samaritan1011001]

Thank you for the changes. Just one more important core export update needed but otherwise it looks good to me!

[buddyeorl]

Overall looks pretty close to me. I just have a few suggestions to improve maintainability. I also think there are some formatting issues - I know our repo is currently not set up to auto-format but it would be helpful if you could run these changes through Prettier (the repo should have prettier settings configured)

@cshfang, Oops, I'm on a new machine and realized I hadn't set up any plugins in my IDE. I've now added Prettier and reformatted all the modified/added code. It should be good now:
prettier

[cshfang]

One last small change and I think we're probably good to go. Thanks for bearing with me on this

[cshfang]

Nit: I think this is effectively the same as

if (!button?.DefaultConfig) {

[buddyeorl]

Yes, make sense to me:

removed unnecessary optional chaining operators

[cshfang]

Given the guard clause above and how the spread operator works, I think we can actually condense this:

return {
  button.DefaultConfig,
  button.configPlatform,
}

Since we know button is guaranteed to be truthy by this point and even if configPlatform is nullish, it would spread just fine and we would end up returning the DefaultConfig.

[buddyeorl]

updated here:
removed unnecessary optional chaining operators

[cshfang]

Overall looks pretty close to me. I just have a few suggestions to improve maintainability. I also think there are some formatting issues - I know our repo is currently not set up to auto-format but it would be helpful if you could run these changes through Prettier (the repo should have prettier settings configured)

@cshfang, Oops, I'm on a new machine and realized I hadn't set up any plugins in my IDE. I've now added Prettier and reformatted all the modified/added code. It should be good now: prettier

No worries - really appreciate it

[Samaritan1011001]

@buddyeorl Apologies for the delay here. I was finally able to verify the changes on both Android and iOS devices work properly. However, there are a few lint fixes you'll have to make before we merge. The failing test should give you the info needed. Looking to merge once these are updated.

[buddyeorl]

@buddyeorl Apologies for the delay here. I was finally able to verify the changes on both Android and iOS devices work properly. However, there are a few lint fixes you'll have to make before we merge. The failing test should give you the info needed. Looking to merge once these are updated.

@Samaritan1011001 Thanks for the update! I've addressed the lint fixes and re-run the tests on my end. Everything should be passing smoothly now. Please let me know if there's anything else needed from my side. Appreciate your assistance!