Structured rich text element mapping

[Simply007]

Motivation

Allow Delivery SDK to work with Structured rich text element.

Proposed solution

• Allow model generators to generate rich text elements differently than just a string.
• Fill the structured rich text element model while mapping the data (.NET implementation example)

Additional context

SDK has solid support for the Thymeleaf template engine - string-based rendering of the data. Loading data for "API" endpoints currently require parsing the HTML and create a structure for rich text on the application site.

Sample item with multilevel nested components: https://deliver.kontent.ai/306d7f21-2609-01b0-6e1c-93cbc328a82d/items/rich_text_resolution

Simple pseudocode of the structure

{
  elements: {
    content: [ // rich text element
      {
        headline: { // component/content item
          ..
        },
        section: { // component/content item
          content: [ // rich text element
            {
              headline: { // component/content item
                text: [ // rich text element
                  {
                    text: "inner headline" // text element is an object too
                  }
                ]
              }
            }
          ]
        }
      }
    ]
  }
}

Notes

• text is also the object for interoperability with components
• infinite loop - first version
  • log a warning and does not resolve! WITH PROPER ITEM IDENTIFICATION ERROR MESSAGE

[Olutim]

Hi @Simply007! I've been working with Kontent-ai pretty much recently. I browsed through the project issues tab and I found this enhancement requirement. I would love to work on this enhancement. Could you assign me to it? Thanks!

[Simply007]

Hello @Olutim,

thanks for the interest.

I am no longer the main owner of the repository, so let's pass this to @IvanKiral.

[IvanKiral]

Hello @Olutim

Thanks for your interest in the Java SDKs. 😎

The issue has been there for some time, why do you want to be assigned there? Are you planning to work on it in the near future? Because if not, I would like to keep it open ;). However, if you would like to work on this issue or have some work done already, just submit the PR, and I will gladly do a review for the PR.

Thanks :)

[Olutim]

Hi @Simply007! Thanks for passing my request! 🙌

[Olutim]

Hi @IvanKiral! Thanks for your response! Yeah, I am planning on jumping on it promptly as soon as I am assigned to it. And I asked to be assigned to it because, I might not be able fully commit a whole day or two to it before submitting a PR. To avoid a situation where someone else would be submitting a PR after I have done some works on the issue before my PR. I will be attending to this issue little by little progressively. But I will certainly finish it! Thanks!✌

[IvanKiral]

Sorry @Olutim for delayed response.

Okay I will give the assignment to you :) Have fun with the development part! I am looking forward to the PR, so please do not delay it! :D

[Olutim]

@IvanKiral Alright!

[IvanKiral]

Hey @Olutim. Is there any news about this issue? :)

[Olutim]

Hi @IvanKiral! Yeah, I'm still on it. I should be sending in PR very soon.

[IvanKiral]

Great!