You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I knew that this feature exist but the implementation currently doesn't support meta attributes; I just never used them since they are too hidden away in the UI to be useful for me.
Adding support for this might not be too difficult. Your best bet is to add a special case handling for "image" and "gallery field to the createCollectionField function and try to model the value of the image node as a set containing meta and image fields. Where the image field is the previous value of the image/gallery field and the meta is a new "set" containing the meta fields & values.
If you are successful and the data looks just like the other sets then everything else (processing of nested fields, image node creation, ...) will just work without further modification.
Okay, I gave up 😅
I can't get my head around it and will change my cockpit-model to use sets instead of images and galleries with meta.
Sorry for now. Maybe I'll take on the task in the future, but changing the model is currently easier 😁
Hi,
I'm using a meta field on images inside an gallery:
The model is defined as follows:
However, in my Query I get the following error:
Are you aware of this issue? I'm not complaining about the missing support for markdown inside the meta-element, but about the complete absence of it.
If this is a new issue, I'd be happy to help out, but need a little pointer into the right direction where to begin :)
The text was updated successfully, but these errors were encountered: