content:
type: fields
fields:
title:
label: Name
type: text
pcoSource:
type: PCOEvent
label: pcoSource
Categories:
label: Select
type: select
options:
abc: Option A
xyz: Option X
I observe these custom options getting successfully served to the panel. Apparently, the options are served in the exact same way for both, Select and the extended field pcoSource:
you’ll see that in your custom field there was never a select field rendered.
You can copy the k-select-field template and add type="select" to the attributes in k-input what seems to give you all the functionality of a select field back.
I also thought about the solutions you proposed (copy the template / use a custom page method).
I decided against the custom page method because I prefer a dedicated field. Furthermore, I was not willing to copy the template since this is against my understanding of extension/inheritance in the object-oriented sense.
Is this a peculiarity of Vue.js that templates are not inherited in conjunction with extends or is it Kirby-specific?
Templates are extended just fine. In your case we need to adapt the template to load the correct sub component. It is more the Kirby way of defining which Input component to load than a problem with inheritance.
Do you need to edit the vue part of your field or is it only about an own field and specific options?