Expose raw oEmbed resource data to calling code

Created on 19 October 2018, about 6 years ago
Updated 30 January 2023, almost 2 years ago

Problem/Motivation

Currently the oEmbed resource fetching in core requires that a specific set of data be returned as a Resource type, discarding data from the provider's return. There are two problems with this:

  1. Non-standardized returns cannot use their meta, such as SoundButt XML using dashes instead of underscores (https://soundbutt.com/oembed?url=https://soundbutt.com/forss/flickermood). I know this is an issue on their end, but is a common one among 3rd parties
  2. There is no direct access to the provider meta data in the case the provider has extra meta attached to a response

Proposed resolution

Add a method that supports returning the provider response.

Feature request
Status

Needs work

Version

10.1

Component
Media 

Last updated about 8 hours ago

Created by

🇨🇦Canada b_sharpe

Live updates comments and jobs are added and updated live.
  • Needs change record

    A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • The Needs Review Queue Bot tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

    Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

    Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.

Production build 0.71.5 2024