Description

When deleting an entity having content through one or more containers, the child entities are orphaned but not deleted. On sites with a lot of content, the amount of orphaned entities can build up fast and can unnecessarily increase the database size.

Expected result

Delete child entities when the host entity is deleted.

• Add phpstan.neon config file referencing the wmcodestyle rule files (example)
• Add phpstan analyse to the coding-standards composer script
• Add autoload-dev entry to ensure autoloading during analysis

Summary

Move custom form alters to the module or find another way to make the form look decent by default.

Motivation

In all of our projects using this module, we're altering the master form to a certain way. Without these alters, and without using our backend theme, the form looks a bit broken. We should improve the default appearance of the form on other sites and other themes.

Summary

Automatically remove bundle from config when it's deleted.

Motivation

Saves time.

Summary

Currently editors often have pages with lots of contentblocks in their main language.
But the translated versions of those pages contain less blocks due to it not being the native language of most editors, a shortage of translators or financially not feasible to translate all pages.

We want to help our editors solve this problem by making it possible to translate snapshots using external services (DeepL, Google Cloud Translation API, ...).

Why update this module

As #44 points out, the Snapshot functionality is largely undocumented.
The module has only defined a set of interfaces and an abstract class to make it possible to implement it. Intentionally done that way to see what different solutions would pop up. Before choosing one to embed in this module as a submodule.
So far we (Wieni) have only used it twice in custom modules and both times use Drupal's serialization module to serialize contentblocks to arrays.

To provide the translation feature I talk about above we, however, need to make two changes to this module.

1️⃣ Snapshot needs to store the original langcode

When we create a Snapshot of a host, we should store the language of that host in the Snapshot.
👉 Add a source_langcode field to Snapshot entity type.

2️⃣ SnapshotBuilderBase::denormalize() needs to accept the source language.

Currently the method accepts array $data, string $langcode.
So we have the serialized array of the block and know the language we need to create it in.

But it's not easy to extract the host's language from a block's serialized array.
Now Snaphots have a source_langcode we can use that value and pass it to the denormalize() method.

👉 Pass the Snapshot's source_value to the SnapshotBuilderBase::denormalize() method.
This is being done in the SnapshotService.

Error: Call to undefined method Drupal\wmcontent\WmContentManager::getContainers() in Drupal\wmcontent\WmContentManager->getHostContainers() (line 195 of modules/contrib/wmcontent/src/WmContentManager.php).

https://github.com/wieni/wmcontent/blob/master/src/WmContentManager.php#L195

There are some fields that are constantly being queried but have no index:

• wmcontent_parent
• wmcontent_parent_type
• wmcontent_container

Description

• Clean up unused branches (check Sourcegraph to make sure the branch is not directly required in a composer.json file)
• Switch default branch to main

Summary

Use default entity operations on the master form instead of manually specifying them.

Motivation

• Less useless code
• Show contrib operations like Entity Clone

• protected $child_bundles
• array()
• lines over 160 chars that could easily be split over multiple lines while increasing readability
• remove comments like put it in the table, some internal values and add the operations that provide less information than the 2 lines of actual code that follow it.

• The lack of asymmetric translations can be added as a disadvantage of the paragraphs module
• The existing points should probably be re-evaluated

We're adding ajax'd drag/drop on a project and it would be a great speedup if we could skip reloading the contentform if the form was submitted using ajax.

// \Drupal\wmcontent\Form\WmContentMasterForm::submitForm

if (\Drupal::request()->isXmlHttpRequest()) { 
    $form_state->setResponse(new JsonResponse('ok'));
}

• Remove dependency on wmmodel
• No need to implement ContainerInjectionInterface when it's defined as a service.

@spoit https://github.com/wieni/wmcontent/blob/master/src/WmContentManager.php#L107

bruh...
bruuuuh

Description

When updating to 2.1.0 on a Drupal 9 project we see:

Uncaught Error: Interface "Symfony\Component\HttpKernel\ControllerValueResolverInterface" not found

The ValueResolverInterface got introduced in Symfony 6.2 which is only available since Drupal 10.0

Proposed solution

Update composer.json and readme to indicate the project isn't compatible with Drupal 9 anymore.
Delete the 2.1.0 tag on GitHub and Packagist.
Create a new 3.0.0 tag, to be used in Drupal 10 projects.
Recreate a new 2.2.0 tag.

We currently don't store the created timestamp.

Would be handy ( debugging-wise )