- πΊπΈUnited States Chris Matthews
Seems as though there are 3 paths that could be taken ...
- Won't fix issue and rely on oEmbed Providers, which already includes
hook_oembed_providers_alter()
- Implement
hook_oembed_providers_alter()
in Core per the original proposed resolution in the IS - Re-scope this issue to assist oEmbed Providers as Chris Burge detailed in #71 β¨ Provide hook_oembed_providers_alter() Postponed
What is the will of the council?
- Won't fix issue and rely on oEmbed Providers, which already includes
- πΊπΈUnited States Chris Burge
@Chris Matthews - Thanks for reanimating this issue.
Re #71, the first part is still an issue, but it probably falls under the "would be nice" category. We could break the current
->getAll()
method into two methods. The first [new] method would solely be responsible for fetching (no caching). The second method would be->getAll()
. It would call the first method and then cache the results in key/value before returning the providers list. From a BC standpoint, it would be 100% non-breaking. Then - the oembed_providers module could call the new fetch-only method instead of->getAll()
. Now that I think about it. It would be pretty easy to implement and to add test coverage. This isn't a heavy lift.The second part was addressed in #3296300: Add UI to clear provider list from keyvalue β . If
hook_oembed_providers_alter()
were implemented in core, then I think we would also want to address the caching issue in core - namely how to clear the values cached in key/value if someone doesn't want to wait 7 days. That might be a can of worms not worth opening.What about this?
- Add a new, fetch-only method to the
ProviderRepository
class in core. - Keep
hook_oembed_providers_alter()
in contrib.
- Add a new, fetch-only method to the
- πΊπΈUnited States Chris Matthews
- Add a new, fetch-only method to the ProviderRepository class in core. π― β π
- Keep hook_oembed_providers_alter() in contrib. π― β π
Both make sense to me.
- πΊπΈUnited States Chris Burge
I dove into
ProviderRepository
, and now that I'm in the code, I'm seeing it's going to be a bit more challenging to refactor->getAll()
into two methods. We'd also have to updateProviderRepositoryInterrface
, which creates a BC issue. So - on second thought, let's not move forward on that.In terms of this issue, I think we're good to change the status to 'Closed (won't fix)'.