1.1.0

[mglaman]

Backwards compatibility warning

1.1.0 has introduced a breaking change in the configuration schema. See below for more information.

What's Changed

• Test drupal container related type inference by @brambaud in Test drupal container related type inference #227
• BrowserTestBaseDefaultThemeRule false positives with UpdatePathTests by @mglaman in BrowserTestBaseDefaultThemeRule false positives with UpdatePathTests #235
• Update branch alias in composer.json by @jibran in Update branch alias in composer.json #236
• Test EntityInterface return type by @brambaud in Test EntityInterface return type #237
• Allow magic methods for variables of type FieldItemListInterface by @eiriksm in Allow magic methods for variables of type FieldItemListInterface #244
• Support entity query execute dynamic return type whether it is a count query or not by @brambaud in Support entity query execute dynamic return type whether it is a count query or not #241
• Support entity class return type extension from entity storage methods by @brambaud in Support entity class return type extension from entity storage methods #239
• EntityDataRepository for entity type data by @mglaman in EntityDataRepository for entity type data #250
• Use entity storage class inferred from entity type by @mglaman in Use entity storage class inferred from entity type #251

Full Changelog: 1.0.3...1.1.0

Configuration changes

The drupal.entityTypeStorageMapping allowed specifying what storage classes were used for different entity types. With #239, support was added to specify what entity class an entity type uses. With #250 the way entity type information is configured has been changed.

Previously:

parameters:
	drupal:
		entityTypeStorageMapping:
			node: Drupal\node\NodeStorage
			taxonomy_term: Drupal\taxonomy\TermStorage
			user: Drupal\user\UserStorage

Now there is an entityMapping property so that we can handle future enhancements with entity type static analysis.

parameters:
	drupal:
		entityMapping:
			node:
				class: Drupal\node\Entity\Node
				storage: Drupal\node\NodeStorage
			taxonomy_term:
				class: Drupal\taxonomy\Entity\Term
				storage: Drupal\taxonomy\TermStorage
			user:
				class: Drupal\user\Entity\User
				storage: Drupal\user\UserStorage
			block:
				class: Drupal\block\Entity\Block

---

This discussion was created from the release 1.1.0.

[eiriksm]

OK, so here's a question:

Maybe we should already be thinking about bundle classes? Coming in Drupal 9.3? https://www.drupal.org/node/3191609

That being said. This is, amazing work. Totally awesome!

[mglaman]

Good question! I thought about it. I also thought I opened an issue, but I did not. I got caught up on the following problem:

There is a problem with bundle classes: we have no way of knowing a bundle of an entity when it is loaded. I think this will fallback on users properly using instanceof checks and assert() to verify an entity if of a bundle and its bundle class.

[eiriksm]

Sounds good. Real easy fix, and it's probably not like people will not do that (or annotating) and expect phpstan-drupal to know...

[mglaman]

What we could do is make sure it returns a union type of the base entity class and any known bundle classes. That'd be better than nothing