I might be completely wrong here, but StringLongItem extends StringItem, but removes the max_length restrictions? Shouldn't that be the other way araound: the least restrictive as base?
I guess the even "bestest" option would be an abstract StringItemBase as base, and extend that into StringItem and StringLongItem?
| Comment | File | Size | Author |
|---|---|---|---|
| #4 | drupal-stringitembase-2383277-4.patch | 4.86 KB | mrharolda |
Comments
Comment #1
mrharolda commentedComment #2
mrharolda commentedComment #4
mrharolda commentedOk, this patch should apply cleanly.
Comment #5
mrharolda commented... and will need a review. You'd think that I'd know how to submit patches by now.
Comment #6
yched commentedI think that's a very good idea. That's how Text*Item are structured for formatted text fields, and it makes more sense IMO.
In #2381079: Adjust storage_settings schema for string_long field type there was the question of how to express the config schema for the settings of those field types, and we removed the "inheritance" on the config schema side. This would make the actual code consistent with that.
Needs review for the testbot to run, but RTBC if tests are green.
Comment #7
chx commented@yched you can always set to RTBC -- the bot will set to CNW if the patch fail.
Comment #8
yched commented@chx: sure, i's just that the #5 & #6 were crossposts - the issue was still NW when I started to write #6, so I didn't want to go straight from NW to RTBC :-)
But sure, RTBC +1 (that is, if the bot decides to catch it at last ?)
Comment #9
mrharolda commentedToo bad there's no 'RBTC + tests ok' status ... or 'RBTC + test pending'?
Anyway: it passed ;)
Comment #10
chx commentedWhat I meant to say is that i believe bot is testing RTBC issues as well these days.
Comment #11
alexpottNice clean-up. This issue is a normal bug fix, and doesn't include any disruptive changes, so it is allowed per https://www.drupal.org/core/beta-changes. Committed 1990524 and pushed to 8.0.x. Thanks!