Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

On fronts, prioritise replacement images over cutouts for pieces with the Comment tone #25490

Merged
merged 1 commit into from
Sep 21, 2022

Conversation

jonathonherbert
Copy link
Contributor

@jonathonherbert jonathonherbert commented Sep 15, 2022

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

Before After
Screenshot 2022-09-15 at 11 34 47 Screenshot 2022-09-15 at 11 39 13

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?

  • AMP
  • Apps
  • Other (please specify)

Does this affect GLabs Paid Content Pages? Should it have support for Paid Content?

  • No
  • Yes (please give details)

Does this change break ad-free?

  • No
  • It did, but tests caught it and I fixed it
  • It did, but there was no test coverage so I added that then fixed it

Does this change update the version of CAPI we're using?

Accessibility test checklist

Tested

  • Locally
  • On CODE (optional)

@jonathonherbert jonathonherbert changed the title Bump fapi-client On fronts, prioritise replacement images over cutouts for pieces with the Comment tone Sep 15, 2022
@jonathonherbert jonathonherbert marked this pull request as ready for review September 15, 2022 10:43
@jonathonherbert jonathonherbert requested a review from a team as a code owner September 15, 2022 10:43
@oliverlloyd
Copy link
Contributor

Do you see the same overridden image in your test when adding ?dcr to the end of the url?

@jonathonherbert
Copy link
Contributor Author

jonathonherbert commented Sep 15, 2022

I'll check – for my own understanding, does DCR use the output of facia-press?

edit: no, DCR doesn't do this – at the time of writing, https://m.code.dev-theguardian.com/jon and https://m.code.dev-theguardian.com/jon?dcr differ in that DCR does not override correctly.

Copy link
Member

@AshCorr AshCorr left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Happy to approve to get this issue fixed. Would be good to investigate why this doesn't work on DCR though, it also uses the output of facia-press so its a bit weird that this doesn't fix it in DCR. Raised guardian/dotcom-rendering#6028

@jonathonherbert jonathonherbert merged commit 7ab26c4 into main Sep 21, 2022
@jonathonherbert jonathonherbert deleted the jsh/bump-facia-scala-client branch September 21, 2022 12:42
@prout-bot
Copy link
Collaborator

Seen on PROD (merged by @jonathonherbert 16 minutes and 37 seconds ago)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants