Contextual links are missing in the wiki entry entity

Don't waste too much time here, this isn't really important. Skip it, if it and leave as-is, if it takes more than 15min.

@thomas.frobieter still missing, any ideas how to fix?

We are already rendering the entity in full view mode, so I am unsure why the contextual links are not added automatically.

/**
   * Converts the BaseFieldDefinitions to a WikiEntry object.
   */
  public function toValueObject(): ProjectWikiValueObjectInterface {
    $view_builder = \Drupal::entityTypeManager()->getViewBuilder('project_wiki_entity_content');
    $content = $view_builder->view($this);

    return new ProjectWikiValueObject('project_wiki_entity_content', $this->get('id')->value, $this->get('langcode')->value, $this->get('category')->value, $this->get('title')->value, $content, $this->get('isDeveloperContent')->value);
  }

Maybe we need to add content_attributes?

<div {{ content_attributes.addClass(['project-wiki-entry__teaser', 'list-js-content']) }}>
        {{ content }}
      </div>

@thomas.frobieter then it sounds like it's not worth it? Maybe we'll find the reason and resultion one day?

I think I get what's the problem here. It's not a semantic one, since even after manually adding the contextual-region class via twig does not make anything appear even though the contextual library is properly loaded on the page.

The actual issue is that we in fact are not actually rendering a real entity here, despite it looking like that. Even though we discussed it before (“it's rendered in full view mode”, etc.) that is not what is happening. The controller asks the plugin manager to gather all wiki entries from all providers, meaning both markdown and content entities. And to turn both types into a compatible format we convert them both to ProjectWikiValueObjects via their plugin definitions. These value objects are not Drupal entities though but rather simple PHP classes. So it is clear that the contextual links library does not think of the rendered output as a place to attach links to even though the contextual class is there. It simply does not know what to do with it.

So I do not see a feasible way to implement this. Either we try for something like a links.contextual.yml which could be really cumbersome to get it to work specifically for content entries, or we find out what makes the contextual links library think that some rendered content is a content entity.

links.contextual.yml would be too much.

We either find a way to render it "regularly" somehow or build a workaround for content entities for now.

@thomas.frobieter this is what copilot says:
https://copilot.microsoft.com/shares/WkTEFtXmdrfzbs2x3Ca31

So maybe we're just missing {{ title_suffix }} ?

@thomas.frobieter, do you have a way to discern what kind of entry (markdown or content) is rendered in twig? Or should I add a parameter for you?

Glad that thinking ahead pays out at least sometimes, even if three years later... :D