As the title says, the PR will contain minor fixes that will make the module more flexible. These fixes include mainly hardcoded strings that can be abstractified.

Issue fork meta_entity-3270884

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

idimopoulos created an issue. See original summary.

idimopoulos opened merge request !2

dimilias’s picture

dimilias commented
Assigned: dimilias » Unassigned
Status: Active » Needs review

claudiu.cristea made their first commit to this issue’s fork.

claudiu.cristea’s picture

claudiu.cristea
Primary language Romanian
Location Arad 🇷🇴
commented

Credits

dimilias’s picture

dimilias commented
Status: Needs review » Needs work

Tests fail with PHP 8.1 though the problem seems to reside with the new PHPUnit and the phpunit.xml. Should we disable the test for now? Other than that it seems OK.

claudiu.cristea’s picture

claudiu.cristea
Primary language Romanian
Location Arad 🇷🇴
commented
Status: Needs work » Reviewed & tested by the community

Nice!

claudiu.cristea’s picture

claudiu.cristea
Primary language Romanian
Location Arad 🇷🇴
commented
Status: Reviewed & tested by the community » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

pfrenssen’s picture

pfrenssen
Location Sofia
commented

If I am reading this correctly, we can now define custom entity types to serve as the meta entity? So this would enable users to create their own entity type with base fields, to store the data efficiently in a single table, rather than having to define bundles on the meta entity type that ships with the module?

This is amazingly useful!! Can you add an example of how to use this in the README or the project page?