-
Notifications
You must be signed in to change notification settings - Fork 42
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 a way to supply a fallback image to the Image
component
#163
Draft
fabiankaegy
wants to merge
5
commits into
develop
Choose a base branch
from
feature/add-fallback-image-option-to-image-component
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Add a way to supply a fallback image to the Image
component
#163
fabiankaegy
wants to merge
5
commits into
develop
from
feature/add-fallback-image-option-to-image-component
Conversation
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
ncoetzer
reviewed
Oct 25, 2022
Comment on lines
+20
to
26
"image": { | ||
"type": "object", | ||
"default": { | ||
"id": null, | ||
"fallback": null | ||
} | ||
}, |
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.
@fabiankaegy Essentially, I think we could have gone two ways about this:
- The way you approached it here by using a single prop structured as an object with two values, i.e.,
id
&fallback
, respectively. However, I'm just wondering about any possible confusion about what type of data needs to be provided for these two values, i.e., number vs. string. - OR perhaps it would be more clear (and less complex) to define the fallback image URL as a separate prop (optional), e.g.,
"imageId": {
"type": "number",
"default": null
},
"fallbackImageUrl": {
"type": "string",
"default": ""
}
…e-component # Conflicts: # components/image/index.js
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description of the Change
This is an exploration of how we could potentially handle adding a fallback image option to the image component.
Closes #161
How to test the Change
Changelog Entry
Credits
Props @ncoetzer @sudar @ajmaurya99
Checklist: