A client asked me to look at a configuration issue they were having, assuming that this was their fault. After a bit of digging I’ve realized it’s anything but. - the current “correct” way with reactions to swap for requires it be referred to using three different identifiers.
Starting where they did with discourse reactions enabled reactions the is referred to as “+1”. Ok, that makes sense.
Finally, changing the icon requires setting discourse reactions like icon. Which of those two permutations is required? Is it +1? How about 1? Nope, both of those result in a missing icon. It’s “thumbs-up”:
For one the drop down should replicate the name of the emoji correctly.
The other field needs to indicate what data it’s expecting.
If you have three fields which to the uninitiated refer to exactly the same thing, then it’s pretty reasonable to expect that they should be populated with exactly the same data. Aliasing the emojis or most common FontAwesome icons would be an easy way to achieve this for the bulk of cases. Directing them where to find the right names would be another.
The missing + in the drop-down is unfortunate because it just compounds the confusion.
Absolutely- any of the regulars here know the inside baseball and secret handshakes to get this stuff working.
Getting real-world feedback from users who I usually consider to be technically adept suggests that anyone else is going to struggle with the current incarnation.
Right, the requests go right back to 2013. In personal/community settings the heart is probably fine, but for any professional environment I’m usually asked to swap it for the .
for 
requires it be referred to using three different identifiers.
is referred to as “+1”. Ok, that makes sense.
I think this cropped up the other day too, but may have been eaten by the topic timer. How could we make this easier, do you think?