Content Resolving / Loading for Website Content Controller

[alexander-schranz]

As discussed with @chirimoya we need to create a overall concept about the resolving process for the Website.

Flow Diagram

TODO create flow diagram:

• RouteDefaultsProvide
• ContentController
• ContentResolver
• PropertyTypeResolver / FieldTypeResolver ( ContentType )
• Loader ( ids -> objects )
• Website Normalizer ( objects -> array ) ( Headless responses )

Interfaces

---

• ContentRouteDefaultsProvider::getByEntity(): array{object: DimensionContentInterface /* mergeddimension */}
• ContentController::indexAction(DimensionContentInterface $dimensionContent /* mergeddimension */, bool $preview = false, bool $partial = false): Response
  • ContentResolver::resolve(DimensionContentInterface $dimensionContent /* mergeddimension */): array{resource: ContentRichEntityInterface, ...}
    • Content/SEO/Excerpt
      • TemplateResolver::resolve(DimensionContentInterface $dimensionContent): ContentView([]) // load template metadata, know which resolvers and which loaders
        • PropertyResolver(mixed $data, array $params = [], string $locale): ContentView
    • ObjectLoader/ObjectResolver(array $identifiers, bool $normalize = false): iterable

      return new ContentView([1, 2, 3], []);
      
      return new ContentView([
          new ResolveObject(1, $params['loader'] ?? 'media'),
          new ResolveObject(1, $params['loader'] ?? 'media'),
          new ResolveObject(1, $params['loader'] ?? 'media')
      ], []);
      
      return new ContentView(new ResolveObjectList([1, 2, 3], $params['loader'] ?? 'media'), []);
      
      // after some discussion we mostly will go with this way:
      return ContentView::create('text', $view);
      return ContentView::createResolvable(1, $params['loader'] ?? 'media', $view);
      return ContentView::createResolvables([1, 2, 3], $params['loader'] ?? 'media', $view);

      SplObject<ContentView, [1, 2, 3]);

      <property name="images" type="media_selection">
          <params>
               <param name="loader" value="custom_media_loader" />
          </param>
      </property>

      <controller defaultFormat="json" format="json|html">

      TODO define more

      Hooks

      TODO define how we can hook into process of saving / publishing e.g. writing References

      Open Questions

      • Admin vs Website Resolving
        • Admin currently has also resolvers maybe
      • How to OptIn for Headless / JSON response
        • No <view> = headless mode?
        • Is Hybrid for same template really a usecase? The could still use a custom controller for that edge case?

[alexander-schranz]

@Prokyonn and I had today a meeting we did discuss a few Interfaces. Things we did not yet discuss in detail is headless handling and cachelifetime handling. But we think we can at current state start with the resolving process and look at the details as soon as we implemented a few resolver / loaders.