Use Rabbit Hole values from config field instead of base fields

Created on 27 January 2023, over 1 year ago
Updated 4 August 2023, 11 months ago

Problem/Motivation

In πŸ“Œ Create "Rabbit Hole" field type for overrides Fixed a new Rabbit hole config field was introduced. The scope of this task is:
1) Replace usage of base fields with new config field;
2) Remove base fields from the entity edit form and make sure the values are not saved;
3) Still keep hook_entity_base_field_info() implementations, we'll have to think about BC probably in another task;

Also, the default option for allow_override should be FALSE now. For that we need:
1) Update default settings rabbit_hole.behavior_settings.default.yml and rabbit_hole.behavior_settings.default_bundle.yml
2) Update a lot of tests.
3) Make a specific hook_update_N(). Because previously, the entity without target rabbit hole settings always showed the field on the edit form. This means that in order not to break the expected behavior for sites that already use the module, we must create target entity type settings with the 'allow_override = true'

In the end, clean up the old fields.

πŸ“Œ Task
Status

Fixed

Version

2.0

Component

Code

Created by

πŸ‡ΊπŸ‡¦Ukraine Matroskeen πŸ‡ΊπŸ‡¦ Ukraine, Lutsk

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.69.0 2024