Thread:Luxionmk2/@comment-24462444-20140321210915/@comment-5007614-20140321232048

Good work. I'm still trying to wrap my head around the code. I saw that you went through the trouble of creating those templates for UnitName:Elements, but I guess there's no way around of looking up data with only the ID.

I'm sort of thinking that when a field is asked for with UnitInfo, it should do some extra work. In the following examples, I want to get a "linkable" evointo.

1. Using the templates that are already there to get the result... #

2. I created a new case for UnitProp's switch statement, which is a little bit easier to read: #

3. Here, I experimented by adding an existing variable in unit pages and seeing what would happen. (evointo-link defined in Unit page) #  (evointo-link NOT defined in Unit page) #

I like how the updated Unit template creates those thumbnails + textual links. We should definitely remove evointo/from-link from the Unit pages.

I might add some additional "info" that UnitInfo/Prop can return:
 * rarity-category: stars that links to category
 * element-link: or element-category, either the image or text that links to category
 * starred-thumbnail-display:
 * too-much-info-display:

Basically, the idea is to use UnitInfo to show commonly-used fields, so that contributors don't have to learn how to chain-link templates.

Thanks for laying the groundwork for this :)