-
Updated
Nov 24, 2020 - C
content-delivery
Here are 19 public repositories matching this topic...
-
Updated
Aug 16, 2016 - Go
-
Updated
Oct 26, 2020 - C#
-
Updated
Nov 1, 2020 - CSS
-
Updated
Nov 10, 2020 - Swift
-
Updated
Nov 24, 2020 - Kotlin
-
Updated
Nov 24, 2020 - Less
-
Updated
Nov 24, 2020 - CSS
-
Updated
Nov 24, 2020 - CSS
-
Updated
Jan 7, 2019 - Java
-
Updated
Oct 1, 2020
-
Updated
Nov 25, 2020 - CSS
-
Updated
Oct 24, 2020 - Java
-
Updated
Jan 18, 2019 - PHP
-
Updated
Sep 7, 2020 - C#
-
Updated
Nov 10, 2020 - C#
Improve this page
Add a description, image, and links to the content-delivery topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the content-delivery topic, visit your repo's landing page and select "manage topics."


Motivation
Currently, if you want to have an inline resolver for rich text elements, it is required to register it for all content models. It would be great to have some approach to reduce this necessity.
Proposed solution
Allow defining a default inline rich text resolver as a fallback when no other resolver is used.
Additional context
Proposal #108