On fronts, prioritise replacement images over cutouts for pieces with the Comment tone #25490
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this change?
Bumps
fapi-client
from 4.0.1 to 4.0.2. This includes a fix where images that have been replaced in the Fronts tool do not correctly override cutouts in pieces with the Comment tone.For more details, see the relevant PR.
How to test
Deploy to CODE, and add a piece with a Comment tone to a front in CODE. Preview the front. Prior to this change, you will not be able to replace the image in the fronts tool. After it, that should work.
Does this change need to be reproduced in dotcom-rendering ?
I'm not sure – my assumption would that the DCR fronts renderer uses the output of
fapi-client
. If that's not the case, let's reconsider.Screenshots
What is the value of this and can you measure success?
This should forestall the e-mail we get every few months or so from a rightly confused Fronts editor.
Checklist
Does this affect other platforms?
Does this affect GLabs Paid Content Pages? Should it have support for Paid Content?
Does this change break ad-free?
Does this change update the version of CAPI we're using?
Accessibility test checklist
Tested