- 🇺🇸United States smustgrave
Please include an interdiff and how the previous patch didn’t apply to receive credit for rerolling
- Status changed to Needs review
over 1 year ago 1:42am 4 April 2023 - 🇳🇿New Zealand danielveza Brisbane, AU
This has been blocked on tests for awhile, so added a test based on the patch in #15.
Ideally we wouldn't introduce a new test class for this and just include it in
DatelistElementFormTest
, but I wasn't sure about the best approach for this. Happy for suggestions - Status changed to Needs work
over 1 year ago 12:31pm 4 April 2023 - 🇧🇪Belgium borisson_ Mechelen, 🇧🇪
Some small phpcs things still need to be fixed in the last patch. The test looks good at first glance, personally I'm not that worried about adding new test classes in kernel tests.
- Status changed to Needs review
over 1 year ago 9:50pm 4 April 2023 - 🇳🇿New Zealand danielveza Brisbane, AU
Looks like a random fail. Seeing back to NR and requing tests
- Status changed to Needs work
over 1 year ago 2:45pm 5 April 2023 - 🇺🇸United States smustgrave
Are the changes to
testDatelistElement changes needed? It passes with or without the fix.
- Status changed to Needs review
over 1 year ago 10:35pm 5 April 2023 - 🇳🇿New Zealand danielveza Brisbane, AU
Those changes are there to assert that you still get the correct error when you have not included
#required_error
.It would be passing without the patch because that was the only error that could be displayed. Now that we support #required_error we need to assert the existing error still displays when you don't have
#required_error
on the element. - Status changed to RTBC
over 1 year ago 1:15am 6 April 2023 - 🇺🇸United States smustgrave
Ah thanks for that @DanielVeza don't mind marking then
- Status changed to Needs work
over 1 year ago 2:21am 6 April 2023 - 🇦🇺Australia larowlan 🇦🇺🏝.au GMT+10
+++ b/core/tests/Drupal/KernelTests/Core/Datetime/DatelistElementRequiredError.php @@ -0,0 +1,87 @@ +class DatelistElementRequiredError extends KernelTestBase implements FormInterface {
Can we reuse the existing test here? we could use a data provider to pass required error and expected error.
Would also be good to get a red/green set of patches showing the test catches the bug.