Closed (fixed)
Project:
Drupal core
Version:
8.7.x-dev
Component:
views.module
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
28 Apr 2018 at 14:43 UTC
Updated:
5 Dec 2018 at 16:29 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
walkingdexter commentedPatch with proposed resolution.
Comment #3
dawehnerNice! Do you mind expanding the test in
core/modules/views/tests/src/Kernel/Plugin/DisplayExtenderTest.php / \Drupal\views_test_data\Plugin\views\display_extender\DisplayExtenderTest??Comment #4
walkingdexter commentedThe changes relate to the validation of the view, and not to the display extenders. Testing the validation of the view is already implemented in \Drupal\Tests\views\Kernel\ViewExecutableTest.
Comment #5
borisson_Either way, we need tests to ensure that this behavior doesn't regress over time.
Comment #6
walkingdexter commentedOk, what tests are needed? I mean, if we expand the test
\Drupal\views_test_data\Plugin\views\display_extender\DisplayExtenderTest, then what functional needs testing? Just checking that the validation of display extender returns correct errors?Comment #7
borisson_#6 yes. Just checking that we return the correct errors is exactly what we need :)
Comment #8
walkingdexter commentedAdded testing of validation.
Comment #10
walkingdexter commentedAdded testing of validation [2].
Comment #11
borisson_I think the tests here look really solid and it looks like it tests the correct thing.
Comment #12
lendudeDo we need a CR for this? Since this could 'break' existing sites (well they would have been broken, but silently, and after this change, it won't be silent anymore).
Comment #13
catchLet's add the change record, CNW for that and tagging.
Comment #15
walkingdexter commentedCreated a change record => https://www.drupal.org/node/2986918
Comment #16
andypostLooks great to go
Comment #17
alexpottCommitted b659cbd and pushed to 8.7.x. Thanks!