Field name restrictions

Hi!

Found an bug (undocumented behavior?):

If custom field have name starting with “pod” (for ex.: pod_phone_number), and i try to use this in pods template ({@pod_phone_number}) – template parsing not working (result – {pod_phone_number}).

I understand, that “pod” may be a reserved word in templates, but did’nt found this info in docs.

Thanks!