inclusion in *from not being interpreted

Support Ticket

+status
answered
 

I'm thinking the emails sent in fortzed should be from the current user.

 

This will be relevant on the invitation emails as well.


Can't do it yet. Rendering is all-or-nothing, so we can't currently render those fields without turning email addresses into mailto links. This will have to be done by using a Text renderer on the email address fields. I guess that needs to happen too. Sigh. add PlainText renderer

  --Ethan McCutchen.....Sun Mar 20 09:58:29 -0700 2011


Sounds like a confusing name. It's not going to be applied to PlainText/Phrase cards generally, right?

  --John Abbe.....Sun Mar 20 18:55:08 -0700 2011


renderers are a code namespace. The HtmlRenderer isn't just for html cards.

  --Ethan McCutchen.....Sun Mar 20 21:18:43 -0700 2011


Got it. But HtmlRenderer is applied to HTML cards, right? Still wondering if PlainText is the best name for this renderer. Is it just for this narrow case of not rendering email addresses, and if so would something like NoEmailRenderer make more sense? If it's different from the default renderer in other ways, how?

  --John Abbe.....Sun Mar 20 22:37:43 -0700 2011


Heh, no, this is not related to cardtypes at all, it's about formats. Just trust me on this one. You'll never see this unless you get into the code.

  --Ethan McCutchen.....Mon Mar 21 08:33:06 -0700 2011


We'd probably actually just call it TextRenderer. Shorter.

  --Ethan McCutchen.....Mon Mar 21 08:58:23 -0700 2011


I know I won't see it, was just trying to be helpful with naming code stuff in useful ways. Letting go...

  --John Abbe.....Mon Mar 21 10:14:53 -0700 2011


add TextRenderer

  --John Abbe.....Mon Mar 21 10:21:17 -0700 2011