Problem/Motivation
This is a follow up to #3076447: Migrate D7 entity translation revision translations to add a comment field to the 'et' content type that was added in the original issue.
+++ b/core/modules/migrate_drupal/tests/src/Kernel/d7/FieldDiscoveryTest.php
@@ -75,6 +75,7 @@ public function setUp(): void {
+ 'et' => 'comment_node_et',
The necessary corresponding field_config_instance table row was not created. This means the current drupal7 fixture is wrong/broken. 😬
Proposed resolution
Add it.
Update tests d7/MigrateCommentField and d7/MigrateCommentFieldInstance
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
Comments
Comment #2
wim leersComment #3
quietone commentedNice. How did you notice this?
Tests should be added to d7/MigrateCommentFieldTest and d7/MigrateCommentFieldInstanceTest as well.
Comment #4
wim leersThanks to #3097336: Improve the DX for migrating content entities: view modes, fields, formatters, widgets etc should be migrated per entity type + bundle, which contains:
Comment #5
quietone commentedThis adds assertions to MigrateCommentFieldTest and MigrateCommentFieldInstanceTest. No interdiff because the change it two lines in an already small patch.
Comment #6
quietone commentedTitle was a bit unwieldy, shortened to the action being taken here.
Comment #7
quietone commentedAnd after all that I forgot the most important thing. Thank you, @Wim Leers for finding the problem and posting a patch!
Comment #8
wim leers🥳🙏
Comment #11
catchCommitted/pushed to 9.1.x and cherry-picked back to 8.9.x, thanks!
Comment #14
quietone commentedUnfortunately, this introduced a 'bug' into the Drupal7 fixture.
There is no field_id '54' and this causes failures when using the fixture via the UI. The field_id should be '1' as used by other comment fields.