Josh Smith

I'm seeing some "usage" notes in here that don't seem to represent actual usage but things about the test setup. Is there a better way we can be handling this?

No I mean, isn't the usage supposed to be the handlebars? Or am I confused?

@begedin could we have your thoughts here on this?

To me the bottom code is useful (the `hbs`) to render, whereas the top part (sandboxed data) being rendered feels not as useful and perhaps even confusing to someone reading...

For me, pending that change, getting tests passing again, and giving me some time to take it for a spin, I would then consider this mergeable and we can create...

I'd also love to see a follow-up issue to expand our documentation (perhaps with a link to the wiki for easier doc-writing) to include some thoughts on how we intend...

Looks like test failures are just `eslint`, btw.

The component probably needs to be able to: - trigger a resend - if the email has hard bounced, needs to not be retryable - ability to update the email...

Btw, good work throwing this in the "improve" milestone rather than "launch". Good sense of product focus. 🙌

@begedin ping again on this question.