Blueprint of a field in frontend

Kirby 3 Questions 🤔
1

Is there proper solution to get the blueprint of a field in templates?

Something like:

blueprint($my_field)
$my_field->blueprint()

It could be really useful for:

  • Self-acting field methods
  • Getting options of structure, tags, radio…
  • Sometimes the label could be helpful
    …

The parent (page) of a field could deliver that information, but once you work with objects like blocks it is almost impossible to get there.

I’m thinking of a daisy chain variable in the content object, that stores his content parents. Similar to the endpoints in the panel.

Featured topic: Get the blueprint panel field type in the template

2

No, the only way to get there is via the parent. The field object doesn’t have its own blueprint, as it can be defined anywhere (own blueprint, file, user, page, block), and even change if fields have their own blueprint defined, it might be extended in different contexts.