>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3582692. --> Reported by: [jrockowitz](https://www.drupal.org/user/371407) Related to !4 >>> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>The Entity labels and Field labels exporters currently derive their scope from entity types with bundles. This makes the export list broader than needed and does not let site builders limit the output to the entity types they actually manage through this module.</p> <p>The module should provide configuration for the entity types included in exports. The default configured entity types should be:</p> <ul> <li>node</li> <li>media</li> <li>user</li> <li>taxonomy_term</li> <li>block_content</li> </ul> <p>The module also needs to support <code>user</code> for field labels even though it does not have bundles.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Add module configuration for the entity types included in Entity labels and Field labels exports.</p> <p>Add a settings form that uses <code>#config_target</code> and stores the selected values in:</p> <p><code>entity_labels.settings:entity_types</code></p> <p>Implementation expectations:</p> <ul> <li>Add a module settings form for selecting exportable entity types.</li> <li>Use the config property <code>entity_types</code>.</li> <li>Use <code>#config_target</code> on the form element instead of manually loading and saving the value.</li> <li>Default the configuration to <code>node</code>, <code>media</code>, <code>user</code>, <code>taxonomy_term</code>, and <code>block_content</code>.</li> <li>Update the Field labels exporter so configured non-bundle entity types such as <code>user</code> can be exported.</li> <li>Treat non-bundle entity types as having a single implicit bundle equal to the entity type ID for field-label export and import. For example, <code>user</code> field rows use <code>entity_type = user</code> and <code>bundle = user</code>.</li> <li>Update field-label import, report, export, and route/title behavior as needed so this implicit-bundle pattern works consistently for <code>user</code>.</li> <li>Keep Entity labels bundle-based. Configured entity types without bundles should not produce Entity labels rows unless separate support is added in a follow-up issue.</li> <li>Preserve the existing per-request entity type and bundle filters so they continue to narrow the configured set.</li> </ul> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <ul> <li>[ ] Add default configuration for <code>entity_types</code>.</li> <li>[ ] Add the settings form and route/link integration.</li> <li>[ ] Update field-label export logic to support configured non-bundle entity types such as <code>user</code>.</li> <li>[ ] Update field-label import logic to support the implicit bundle value for non-bundle entity types.</li> <li>[ ] Ensure configured non-bundle entity types do not break Entity labels export/report behavior.</li> <li>[ ] Add or update automated test coverage for defaults, configuration filtering, and <code>user</code> field-label export/import.</li> <li>[ ] Update the README if needed.</li> </ul> <h3 id="summary-ui-changes">User interface changes</h3> <p>A new admin settings form will be added so site builders can choose which entity types are included in exports.</p> <h3 id="summary-api-changes">API changes</h3> <p>A new module configuration property will be introduced:</p> <p><code>entity_labels.settings:entity_types</code></p> <p>No new public PHP API is required.</p> <h3 id="summary-data-model-changes">Data model changes</h3> <p>New module configuration is added for the selected entity types. No database schema changes are required.</p>