The booking line entity is declared with id yoyaku and base_table yoyaku (src/Entity/Booking.php). It is the only entity that breaks the yoyaku_* naming every sibling follows: yoyaku_resource, yoyaku_slot, yoyaku_transaction, yoyaku_venue, yoyaku_seat, yoyaku_section. The bare yoyaku name is ambiguous (it reads as the module, not a booking) and makes the schema harder to navigate.

Rename the entity type id, and its base table, from yoyaku to yoyaku_booking. Pre-1.0 with no released backwards-compatibility surface is the right moment.

Scope:

  • src/Entity/Booking.php: the id and base_table keys.
  • The PHP references to the entity type id (getStorage, entity-type-id checks).
  • The views base-table configuration in the *_views submodules (views built on the yoyaku base table).
  • A by-hand rename of the live yoyaku table: it is non-revisionable and non-translatable, so the base table plus any yoyaku__* multi-value field tables; pre-1.0 there are no update hooks.
  • Verify the yoyaku_orchestra bridge and any consumer do not hardcode the old id.

target_type: yoyaku appears in no configuration, so there is no entity-reference churn. Split out from the cancellation work in #3612196.

Issue fork yoyaku-3612365

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

mably created an issue. See original summary.

mably opened merge request !67

mably’s picture

mably commented
Status: Active » Needs review

  • mably committed 22853512 on 1.x 
    task: #3612365 Rename the booking entity type from yoyaku to...
mably’s picture

mably commented
Status: Needs review » Fixed

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.