Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
ConfigStorageController::importChange() doesn't work for protected properties.
Tests and fix coming tomorrow.
Comment | File | Size | Author |
---|---|---|---|
#11 | config-1889854-10-FAIL.patch | 2.51 KB | tim.plunkett |
#11 | config-1889854-10-PASS.patch | 3.28 KB | tim.plunkett |
#11 | interdiff.txt | 3.54 KB | tim.plunkett |
#7 | config-1889854-7.patch | 4.13 KB | tim.plunkett |
#7 | interdiff.txt | 2.22 KB | tim.plunkett |
Comments
Comment #1
tim.plunkettOkay, this needs a test using the config_test config entity, so I'll work on that, but at least I have something.
Comment #3
tim.plunkettOh, that actually wasn't that hard.
This is a pretty big one, since Views cannot be updated at all.
Comment #5
tim.plunkettHad to adjust the expectations of other tests, and reorder the properties.
Comment #7
tim.plunkettAhh, had to adjust for the config entity query commits.
Comment #8
EclipseGc CreditAttribution: EclipseGc commentedeyup
Comment #9
sunWhy is this part of the UI test?
Let's move it into the API import test.
Can we rename this property to 'protected_property', please?
Comment #10
sunAlso, can we make sure to check for existing issues first? :)
Marked #1892558: Fatal error when importing a view, using set() rather than accessing properties directly might work as duplicate.
Comment #11
tim.plunkettIt turned out we already had test coverage for this in ConfigImportTest, and my addition to ConfigImportUITest was redundant (I put it in there initially because I was writing test coverage to mirror my interaction in the UI).
I also did s/description/protected_property, that's a nice clarification.
Comment #12
tim.plunkettThat was tagged neither Configurables nor VDC, I can't look everywhere.
Comment #13
sunThanks, looks great. :)
Comment #15
tim.plunkettRetested through qa.d.o
Comment #16
webchickCommitted and pushed to 8.x. Thanks!