feat(render): Add useRenderingOptions

[thena-seer]

Summary

For feature request #686 (comment)

Adds useRenderingOptions, which uses a React Context under the hood to pass the rendering options to the template.

Usage:

export const TemplateWithCustomPlainText: React.FC<Readonly<TemplateProps>> = ({ firstName }) => {
  const options = useRenderingOptions();

  if (options.plainText)
    return (
      <>
        <h1>Hello, {firstName}!</h1>
        <img alt="test" src="img/test.png" />
        <p>Thanks for trying our product.</p>
      </>
    )

  return (
    <>
      <h1>Welcome, {firstName}!</h1>
      <img alt="test" src="img/test.png" />
      <p>Thanks for trying our product. We're thrilled to have you on board!</p>
    </>
  )
};

Test plan

unit tests pass

[vercel]

@thena-seer is attempting to deploy a commit to the resend Team on Vercel.

A member of the Team first needs to authorize it.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 20136ef

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[gabrielmfern]

I was thinking about this and I got to the conclusion that the uniqueRenderId would end up being used more often than not, and its ergonomic are not great for common use cases. If you can think of anything that would just work out-of-the-box like useContext lmk.

Let's use a context for now and in the future we'll think about how to make it work with react-markup.

[thena-seer]

Ok, switched back to useContext

[thena-seer]

Although, I'm not sure how to resolve the rsnd build error we're seeing in CI.

[gabrielmfern]

Sorry for taking so long, but I don't think we're going to be able to support it, sadly. For this to be supported, and we'd love to have it, we'd need to rethink how this gets implemented at the core, open to any ideas if anyone has some. But using a context isn't going to be sustainable, and already breaks in our web tests as was happening back in March.