Open miiimooo opened 5 years ago
I also hit this issue after upgrading from v1.4.0 => v2.1.1. I had been setting the sub-fields by way of:
| field_a:country_code | field_a:address_line1 | field_a:locality | field_a:administrative_area | field_a:postal_code |
Which, in v2.1.1, produced:
Notice: Undefined offset: 0 in /vendor/drupal/drupal-driver/src/Drupal/Driver/Fields/Drupal8/AddressHandler.php line 54
Looking at the code in AddressHandler.php, it looked like an adjustment from string keys to numeric keys might work, but at the expense of readability/maintainability down the line.
I instead opted for @mdolnik-eelzee's patch in #236, which seems to work well.
The pull request #240 is the correct way of solving this as discussed in #236
I'm trying to create a profile entity with an address field like this:
And the address field in my feature looks like this:
But since upgrading and now using the AddressHandler it breaks with:
I get another issue when I copy and paste the example in https://github.com/jhedstrom/drupalextension/blob/master/features/field_handlers.feature#L16
Address is v1.4.0 and (v1.6) Drupal extension v4.0.0beta2
Looking at the source there seems to be a custom address field type just for the tests.