BACKLOG-22056: Spike for GraphQL field for richtext nice URLs (Approach Two with RenderEngine) #382
Conversation
This file contains hidden or 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
…specific view and RenderEngine (WorkInProgress)
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.
JIRA
https://jira.jahia.org/browse/BACKLOG-22056
Description
Spike to test another approach for embedded richText URLs rewriting.
We create a simple view for all nodes in order to display a property but apply it only in specific cases to generate a rendered view of richText property.
Integration is done via a GraphQL Property Extension that call the render engine. (like the Node Extension)
Tests
The following are included in this PR
Checklist
I have considered the following implications of my change:
Documentation