Embed Block: fix crash in isFromWordPress helper if preview.html is false #25140
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
…alse The Facebook oEmbed provider returns `html: false` when the URL is not previewable, e.g., when it points to a Facebook page rather than a post or video. The `isFromWordPress` helper used to use Lodash `includes( html, x)` which handles falsy values gracefully. After refactored to `html.includes( x )`, non-string values started to trigger a `TypeError`.
|
Size Change: +2 B (0%) Total Size: 1.2 MB
ℹ️ View Unchanged
|
ntsekouras
approved these changes
Sep 8, 2020
jsnajdr
added
[Type] Bug
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.
The Facebook oEmbed provider returns
html: falsewhen the URL is not previewable, e.g., when it points to a Facebook page rather than a post or video.The
isFromWordPresshelper used to use Lodashincludes( html, x)which handles falsy values gracefully. After a refactor tohtml.includes( x )in #24090, non-string values started to trigger aTypeError.Fixes #25108.