fix(i18n): i18n support, fixes issue #52

[dlabaj]

Added support for i18n to Error Boundary, Inavalid Object, and Unavailable Content.

Fixes issue #52.

https://pf-localization.surge.sh/

[edonehoo]

@dlabaj For the most part, I think what you have is fine, but if I were to edit for consistency & clarity I would make these changes:

Invalid object
- The default values should all use single quotation marks ‘ ‘

• invalidObjectBodyText:
  • The body text for the invalid object message
• invalidObjectTitleText:
  • The title for the invalid object message
• toLandingPageText:
  • The text label for the link that points back to the landing page
• toLandingPageUrl:
  • The URL that the landing page link points to

Error boundary

• headerTitle:
  • The title text to display on the error page
• silent:
  • Indicates if the error is silent
• errorTitle:
  • The title text to display with the error
• errorDescription:
  • The description text to display with the error
• errorToggleText: The text for the toggle link that users can select to view error details
• defaultErrorDescription:
  • The default description text to display with the error if no errorDescription is provided
• children: (I'm not sure if this is true, making assumptions feel free to ignore)
  - Additional components to be rendered in the error boundary screen

Unavailable content

• statusPageLinkText:
  • The text label for the link that points to the status page
• statusPageUrl:
  • The URL that the status page link points to
• unavailableBodyPostStatusLinkText:
  • The body text for the unavailable content message that appears before the status page link
• unavailableBodyPreStatusLinkText:
  • The body text for the unavailable content message that appears after the status page link
• unavailableTitleText:
  • The title for the unavailable content message

[dlabaj]

@edonehoo Updated with your recent comments. Let me know if there is anything else.

[edonehoo]

looks good!

[github-actions]

🎉 This PR is included in version 5.1.0-prerelease.1 🎉

The release is available on:

• GitHub release
• npm package (@prerelease dist-tag)

Your semantic-release bot 📦🚀