Thread:Amrosa/@comment-25956839-20171127182643/@comment-30967537-20171128103953

Having edited and created templates I can see both sides of the "named parsers" debate ...
 * It's so much easier to find the piece of information if it has a name, looking through a line of templated data separated only by pipe | symbols can be quite confusing.
 * It's really useful when you want to change a template, e.g. to add another field, you just stick it in there ... so much easier than having to re-number all your existing fields so the data is grouped logically OR adding it at the end where it's not grouped logically.
 * Placing them on separate lines makes reading and editing easier BUT makes scrolling through a long list (e.g. the Cars page, 199 x 10+ fields) rather painful ... and, ironically, easier to miss something on a smaller-screened mobile device which this change is meant to benefit!

As Dave wrote, swings and roundabouts. Inertia, most people don't like change, having to learn something new. I think it's a good thing as long as the old method continues to work ... I really don't want to have to rewrite all my templates and PQ scripts!

I think there should be a RR3 Wiki naming policy e.g. proper/meaningful names, capitalised words, no spacing, etc ... CarID. Maybe a page with the list of parser/field names, edited as new names are added.