id summary reporter owner description type status component version severity resolution keywords cc stage has_patch needs_docs needs_tests needs_better_patch easy ui_ux 476 use vars values in template {{}} dotted style Sokolov Yura Adrian Holovaty "What if I has two contexts: {{{ s1= Context({'person': {'first_name':'Homer', 'last_name':'Sympson'}, 'first_field':'first_name','second_field':'last_name'}) s2= Context({'person': {'first_name':'Homer', 'last_name':'Sympson'}, 'first_field':'last_name','second_field':'first_name'}) }}} and wish to render template accordinary to field ord? I wrote a tag to get a dictionary value, but I think it is ugly to write a tag when I want to take variable's field. May be better to make this possible: {{{

{{ first_field }}

{{ person.$first_field}}

{{ second_field }}

{{ person.$second_field}}

}}} or even: {{{

{{ first_field }}

{{ person.${first_field} }}

{{ second_field }}

{{ person.${second_field} }}

}}} or {{{

{{ first_field }}

{{ person.(first_field) }}

{{ second_field }}

{{ person.(second_field) }}

}}} or append to resolution order as a last resort: foo[Context[bar]] But it is error prone cause of nested resolution: person.(fields.(num)) could not be written without braces. Or maybe allow filters to access Context Object as Node.render do, then most tags could be implemented as filters and this task would be written simpler. Priority is low cause there are a bit of real life needs. But thinking that it can be possible makes me good. May be it will help to write custom form generator." enhancement closed Template system 1.1 normal wontfix Design decision needed 0 0 0 0 0 0