Nico Hoffmann ෴.
Nico Hoffmann ෴.
1. Easing it with some auto-detection would make it a lot less painful (even though I also think it's super limited how many would be affected). So I'd be all...
@tobimori would you be able to add unit tests for this? honest answer, no grudges if not. only then someone from us would need to pick it up at some...
That's correct since we removed cards and list items in 3.6 as separate components. Please try `image.srcset` instead.
@lukasbestle My first answer would be that mixed types shouldn't be supported. I don't see any logical result that could be expected. So maybe there is a way how we...
@lukasbestle > the select field display is currently broken as well because it does not use v-html for displaying the options We use the standard `` tags which don't allow...
Since this would required some breaking changes, we decided that we could not introduce such a feature before 3.7
We're thinking rather of supporting query syntax and adding a new `t()` helper to the query syntax. ``` myField: label: "{{ t('myfield.label') }}" type: select options: option1: "{{ t('myfield.option1') }}"...
No, I don't think that makes a difference for yaml. Will both be parsed as strings. Do you think anything in the proposed solution would be not ideal?
@medienbaecker gave it a first try and so far haven't run into any major issues. I think right now we are missing some padding at the page end, that should...