- Issue created by @benjifisher
- 🇺🇸United States benjifisher Boston area
We could also fix the problem in the
text
module: either changetext.schema.yml
or overridedefaultSettings()
in the child classDrupal\text\Plugin\Field\FieldWidget\TextareaWidget
. - Merge request !8977Make the default value of rows an int instead of a numeric string → (Open) created by benjifisher
- Issue was unassigned.
- Status changed to Needs work
4 months ago 11:15pm 29 July 2024 - 🇺🇸United States benjifisher Boston area
The MR has the proposed resolution. This is my entry in the contest for this year's smallest change.
I will set the status to NW, not NR, because this bug fix still needs a test.
- 🇮🇳India prashant.c Dharamshala
@benjifisher
I found an existing test for this field type here: StringFieldTest.
https://api.drupal.org/api/drupal/core%21modules%21field%21tests%21src%2...Do you think this test will suffice as is, or do we need to modify it or create an entirely new one? Please advise.
- 🇺🇸United States benjifisher Boston area
@Prashant.c:
Thanks for taking a look at this issue!
That test class is in the
field
module, and it does not enable thetext
module, so I do not think that is the right place for it.Also, we need a test that fails without the change I made in the MR. All current tests are passing, so we need to add a new test, once we decide on where to add it.
I think
Drupal\Tests\text\Functional\TextFieldTest
is the right place.Before doing too much work, check what I said just above "Steps to reproduce": if you add the field from the UI, then you do not run into this problem. If I was right, then you will need to write a test module that implements
hook_entity_base_field_info()
. I can help with that if you want.I am not sure how to test for config validation. But I think we should do that, and not just check the configuration. That is why I think this should be a functional test.
- Status changed to Postponed: needs info
4 months ago 2:28am 3 August 2024 - 🇺🇸United States benjifisher Boston area
I tried to reproduce this issue starting with a fresh install of Drupal core, and I could not.
There must be something else on my site that is causing this odd behavior.
I am postponing this issue now. I hope I will have time next week to look into it some more.