Allow for reason to be included when using tpa

[ghost]

Example usage:

@Pham tpa "Opinion-based"

which would produce something like

Low Quality A (25.2%): two plus two equals jquery ... by SomeUser, on stackoverflow.com. (Reason: "Opinion-based" -UserWhoSentTPA)

[ArcticEcho]

How about rephrasing the report a little?

Opinion-based (UserWhoSentTPA): two plus two equals jquery ... by SomeUser, on stackoverflow.com.

[ghost]

I think that's good. Is it possible to preserve [tag:tagname] markdown within the reason string?

[ArcticEcho]

Yes, that should be possible. But that kinda goes against Pham's traditional report format.

[Unihedro]

Please disable this when TPA is used in the reflector room (i.e. Tavern).

[ArcticEcho]

Will do.

[Unihedro]

As mentioned by @ArcticEcho, the new syntax may look like this for a TPA:

Low Quality A (by TPA'er's name): Aaaabbbbccccddddeeeeffffgggghh, by jay r. t. Roll, on apple.stackexchange.com.

This creates an opportunity for this ticket to simply be extending from the "by TPA'er's name" instead.

[honnza]

It might get confusing who is the J. Random Troll and who is the reporter
here... people will get used to it, but people will make jokes before they
get used to it.

On Thu, Feb 5, 2015 at 5:02 AM, Unihedron notifications@github.com wrote:

As mentioned by @ArcticEcho https://github.com/ArcticEcho, the new
syntax may look like this for a TPA:

Low Quality A (by TPA'er's name): Aaaabbbbccccddddeeeeffffgggghh, by jay
r. t. Roll, on apple.stackexchange.com.

This creates an opportunity for this ticket to simply be extending from
the "by TPA'er's name" instead.

—
Reply to this email directly or view it on GitHub
#39 (comment)
.

[ArcticEcho]

Hmm, good point @honnza. I have an idea, what if I made the report type (i.e., the "Low Quality A" part, or whatever the reason is) a link to the TPA, and on-hover could have the user's name?