#2313757: Remove text_processing option from text fields, expose existing string field types as plain text in UI has split the "text" field types between string* (raw strings) and text* (formatted text).
For consistency, the 'list_text' field type, that is only about unformatted strings, should be renamed list_string.
This is if we don't end up doing #2342581: Merge list field types into main field types. Since this is still being discussed and has no patch, and doing the rename should happen before the beta, posting a patch for this here.
Published change notice and added class rename info too
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 2344979-rename_list_text-1.patch | 13.76 KB | yched |
Comments
Comment #1
yched commentedPatch does :
- field type : list_text --> list_string
- class: ListTextItem --> ListStringItem
- Human readable label is left unchanged, since #2313757: Remove text_processing option from text fields, expose existing string field types as plain text in UI kept "Text" for string* and text* field types.
Comment #2
andypostmakes sense
Comment #3
wim leersPatch looks great + confirmed that zero occurrences of
list_textremain when the patch is applied.RTBC+1
Comment #4
catchCommitted/pushed to 8.0.x, thanks!
Comment #6
anavarreProgrammatically update your custom YML files:
Comment #7
berdirChange record? Maybe part of the one about text/string split-up?
Comment #8
yched commented- Change record created
- added a link to it in the CR about the text/string split-up (see diff)
Comment #9
larowlanComment #10
yched commented@larowlan: thanks, lost the habit of publishing CRs :-)
Adjusted the part about the class rename, since it only affects D8-to-D8