Open twiro opened 3 months ago
@twiro For me, this really boils down to the issue in (A). As you spotted yourself, the preview was initially created for the structure field and then they are getting re-used now for the tables layout of sections. However, we need to fix them that they either really update the page content or that in sections they are display only without any interaction.
(B) works as intended and expected, displaying the content field value as text. We aren't looking up the field type in addition when the column type is defined, it gets treated as that type.
(C) I don't see much value here currently in re-implemnting the logic twice. You can define the texts for the different states on the actual field.
Description:
If a toggle field is included as a column in a list of pages in table layout the preview of the field behaves buggy/irritating:
A) Example A
Blueprint:
Screenshot of the resulting table:
Expected behavior / Problem:
With that preview given (especially as the UI feels fully functional) I'd expect the toggle value to get saved whenever I use a toggle in the table – only, it doesn't!
More Context:
Looks like this preview was originally implementend for the structure field and works there. (Haven't tested that actually)
B) Example B
In the forum I ran across the idea to use
type: text
for the preview of a toggle field in table layout, but that doesn't result in a satisfying experience either:Blueprint:
Screenshot of the resulting table:
Expected behavior / Problem:
If changing the preview of a toggle field to text in a table column is actually possible, I'd expect to see the toggle text values I defined in my blueprint (
Ja
,Nein
) or at least the default text values for the given language (an
,aus
) – but all i get istrue
andfalse
.C) Example C
Thinking about the text values of the toggle field preview a little more neither
true
andfalse
nor the default text values of the given language (an
andaus
) do feel really convincing here – if the values can be customized in the blueprint, the only really satisfying solution for the field preview would be to have it customazible there too. If not automatically, then at least by redefining the values in the columns-settings of the table:Blueprint:
Screenshot of the resulting table:
Expected behavior / Problem:
Apart from the missing saving-functionality described in example A, I'd expect to see
Ja
andNein
used instead ofan
andaus
.Setup / System