[META] Stronger Typing for Entity API

Created on 18 April 2024, 10 months ago

Updated 30 April 2024, 9 months ago

Problem/Motivation

Currently the majority of the Entity API methods (especially id()) do not strongly indicate their return type and in many cases allow a wider return type than is ever utilized.

We should strength the return type.

This is also required for eventual PHPStan L9 coverage

Steps to reproduce

Proposed resolution

Remaining tasks

📌 UserInterface::id(), AccountInterface::id() should return int to match typehints Needs work

User interface changes

N/A

API changes

See child issues

Data model changes

See child issues

Release notes snippet

See child issues

🌱 Plan

Status

Active

Version

11.0 🔥

Component

Entity →

Last updated about 2 hours ago

Maintained by
🇬🇧United Kingdom @catch
🇨🇭Switzerland @berdir
🇩🇪Germany @hchonov

Created by

🇺🇸United States cmlara

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @cmlara
Comment 9 months ago →
🇩🇪Germany jurgenhaas Gottmadingen
Adding a related issue where the status field value is an integer in the content entity while the same value in the original is a string.
Comment 9 months ago →
🇺🇸United States cmlara
Opened 🌱 [META] Stronger Typing for Entity API Active . The scope is wider than just the Entity subsystem, however it is the root cause of some entity issues. It wont solve existing issues, however it will set a standard for going forward.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024