Replies: 2 comments 8 replies
-
Yeah at the moment there is a limited amount of parameters you can set through GraphQL. It is definitely lacking.
As a workaround, continue using Responsive fieldtype, you can set default values in the blueprint to avoid filling out ratio and fit all the time. Like so in your blueprint yaml file: -
handle: responsive_field
field:
use_breakpoints: false
allow_ratio: true
allow_fit: false
restrict: false
allow_uploads: true
display: 'Responsive Field'
type: responsive
icon: assets
listable: hidden
instructions_position: above
visibility: visible
always_save: false
default:
ratio: '1234'
'glide:fit': crop_focal |
Beta Was this translation helpful? Give feedback.
-
v3.1.0 added almost all arguments to have parity with the responsive tag. Additionally now you can pass responsive fieldtype data into responsive field. See PR changes here: #203 |
Beta Was this translation helpful? Give feedback.
-
When using the "Responsive" field in Statamic, you can pick between different options for FIT for the image.
But, when you use the "Assets" field and just use the "responsive" graphql query, there is no option for the FIT to be selected.
Can we make an option to include this? We really love the focal-crops that you provide and it's a shame that we have to define "Responsive" field with no breakpoints and define the ratio all the time just to use the FIT.
If it's possible, can you let us know how to always set the focal-crop to FIT?
Beta Was this translation helpful? Give feedback.
All reactions