Open markszulc opened 4 years ago
Hi @gabrielwalt . We have a need for the variations to be listed in the Content Fragment List too. You'd expect that this was the case to begin with. When can we expect this enhancement?
Same here. We are beginning to see more and more use cases for content fragments that calls for the use of the content fragment and content fragment list component. Providing support for variations as described above would be very useful. I would also add that there should be a toggle in the dialog that determines the fallback behavior. The component by default would return Master variations. But when a specific variation is requested (maybe via text field), it would only return content fragments that match the requested variation unless when the toggle is on, then it would return master variations for fragments that do not have the requested variation.
Feature Request
Content Fragments allow for variations. The Content Fragment List component does not support this. Without this support is not possible to use the CF variation feature without customisation.
The Content Fragment List component should allow the selection of a variation. When rendering the output (both HTML & JSON) it should look for this variation (match by name) and use the content if it exists. If it does not, the default variation is used.