Missing ContentType resolver

[wachterjohannes]

Core Content Types

• [x] media_selection
• [x] block
• [x] page_selection
• [x] single_page_selection
• [x] single_category_selection #45
• [x] category_selection
• [x] contact_account_selection
• [x] single_account_selection
• [x] single_contact_selection
• [x] account_selection #43
• [x] contact_selection #44
• [x] single_media_selection
• [x] image_map #85
• [x] link (new sulu 2.4 content type)
• [x] page_tree_route #119
• [x] smart_content
  • [x] Pages
  • [x] Snippets #123
  • [x] Contacts #122
  • [x] Accounts #122
  • [x] Media
• [x] teaser_selection #83
• [x] snippet_selection #32
• [x] single_snippet_selection #57
• [x] collection_selection #121
• [x] single_collection_selection #121

To complete the list the following content types do not need an own resolver:

• [x] number
• [x] single_select
• [x] select
• [x] checkbox
• [x] color
• [x] time
• [x] date
• [x] email
• [x] url
• [x] location
• [x] password
• [x] phone
• [x] text_line
• [x] resource_locator
• [x] text_editor
• [x] text_area
• [x] tag_selection
• [x] route

ArticleBundle Content Types

• [x] single_article_selection sulu/SuluArticleBundle#622
• [x] article_selection sulu/SuluArticleBundle#622
• [x] smart_content
  • [x] Article sulu/SuluArticleBundle#622
  • [x] ArticlePageTree sulu/SuluArticleBundle#622

FormBundle Content Types

• [ ] form_selection

[alexander-schranz]

For this who want to help bringing the bundle forward a ContentTypeResolver can be created by creating a service in Content/ContentTypeResolver/* folder with the ContentTypeResolverInterface. And register this services with the sulu_headless.content_type_resolver Tag.

They should implement the same parameter which are supported by the sulu core content types which can be found using bin/console sulu:content:types:dump command.

[TheCadien]

@alexander-schranz @wachterjohannes Are you sure that the Tag Selection needs its own resolver? I just wanted to take care of the topic and saw when testing that the tags are already output as a correct looking array. :D

"tags": [ "Test1", "Test2", "test" ]

[alexander-schranz]

@TheCadien Thank you. That's correct I did update the list.

[alexander-schranz]

Also did see that the single_category_selection was not yet in the list that should be really straight forward by having a look at the exist CategorySelection.

[TheCadien]

@alexander-schranz I checked "location" works fine without own type resolver :)

[alexander-schranz]

@TheCadien Thank you!

[TheCadien]

@alexander-schranz seems the "route" content type is full working without any type resolver.

route-test: "/test-url"

[alexander-schranz]

Added the new image_map content type also to the todo list which is shipped with sulu 2.2.

[alexander-schranz]

Added also the new single_snippet_selection content type to the list which was added lately to the 2.x releases. Should be similar to the exist implemented snippet_selection (#32) content resolver.

[alexander-schranz]

Thx to @luca-rath the teaser_selection will be part of the next release #83

[alexander-schranz]

We got 2 new content types the single_collection_selection and collection_selection content type which should be implemented. They are here to provide only the collection data so response should look at current state something like:

{
    "id": 1,
    "key": null,
    "title": "My Collection",
    "description": "Description about the Media"
}

[alexander-schranz]

Added the new link content type to the todo list :)

[TheCadien]

I take on the todo link

[alexander-schranz]

Link content type has been added here: https://github.com/sulu/SuluHeadlessBundle/pull/111

[alexander-schranz]

The missing smart content providers: account, contact, snippets and the collection and single collection selection were implemented.

[Josef-Reichardt]

Maybe the resolver for the single_form_selection content type could be used from https://blog.bitexpert.de/blog/sulu_headless_form_data?

[shochdoerfer]

@Josef-Reichardt happy to contribute our "latest" iteration of that code snippet from our blog post if there's interest.