Closed (fixed)
Project:
Search API
Version:
7.x-1.x-dev
Component:
User interface
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
13 Mar 2011 at 15:51 UTC
Updated:
27 Mar 2011 at 19:11 UTC
Jump to comment: Most recent file
Comments
Comment #1
ygerasimov commentedpatch attached
Comment #2
drunken monkeyI'm not fully convinced that bloating the labels in such a way really makes sense. For one thing, you'll have the same problem afterwards (and on several other places), if you add the fields for both related entities. So usually the best practice will probably be not to give the same name to different fields in the first place. (Although I understand that it makes sense sometimes — I also had this case once.)
Also, machine names are unnecessary for the majority of fields that have different names. Therefore, showing them for all fields is kind of overkill.
How about the attached patch, showing the machine names only when two options would otherwise have the same label? That's one I could live with. (OK, I could live with yours, too, but I prefer a minimal-invasion approach.)
Comment #3
ygerasimov commentedYes your patch is nicer. I added some comments.
Comment #4
drunken monkeyCommitted, thanks!