-
Notifications
You must be signed in to change notification settings - Fork 30
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
Add support for podcast image i n Picture.tsx #12568
Merged
Merged
Changes from 11 commits
Commits
Show all changes
17 commits
Select commit
Hold shift + click to select a range
6ab4692
Revert "Revert "Create new `PodcastMeta` component ""
oliverabrahams 4ca44c5
fixed a few errors
oliverabrahams e71ca74
Merge branch 'main' into e2e/podcast-tags
oliverabrahams fb27194
add podcast cover image first attempt
oliverabrahams 124a238
Add podcast image to StandardLayout.tsx
oliverabrahams 253b8ce
update picture component to accept custom roleType
oliverabrahams 0c0fa28
cascade wrong way round ):
oliverabrahams 45e10b9
Merge branch 'main' into e2e/podcast-tags
oliverabrahams b1af9fd
Merge branch 'e2e/podcast-tags' into e2e/podcast-cover-image
oliverabrahams 33fcb0f
fix merge
oliverabrahams 391ded9
Merge branch 'main' into e2e/podcast-cover-image
oliverabrahams 26e4f0f
Update picture to add new role type, Keeping the decideImageWidths as…
oliverabrahams 52bc208
Update picture to add new role type, Keeping the decideImageWidths as…
oliverabrahams d724c62
Add comment explaining custom role types
oliverabrahams 23cc773
update series tag name
oliverabrahams 3664823
rollback changes to layout as these are in a different PR
oliverabrahams f115221
Merge branch 'main' into e2e/podcast-cover-image
oliverabrahams File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we're going to add more customisation to the
Picture
component, do we want to do it like this, where we add an override that says anything goes, or do we want to add a new flag forisPodcastCover
or something like that?Reason I ask is because of the disclaimer at the top of
decideImageWidths
:With this change, this is no longer the case.
I'll admit it doesn't feel sustainable to have a function that receives a growing series of arguments to account for a possibly endless list of weird and wonderful new use cases. It also doesn't feel good for that function to canonise some widths as "source of truth" and for everything else, there's a custom role. And since this podcast cover image has been around for at least 8 years and is canonised in CAPI and tag manager, maybe dotcom-rendering needs to bite the bullet and accept it as a thing also.
PS I'm away until Thursday so please overrule me if, in general, there's disagreement on this point. I don't want my absence to be a blocker.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The extra argument way you suggested seems to be how many of these components work in DCR. Also I don't want to break that contract about the source of truth. I will change it happily to use a prop through the Picture component as suggested.