Closed (fixed)
Project:
Drupal core
Version:
11.x-dev
Component:
field system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
20 Jul 2023 at 14:11 UTC
Updated:
11 Aug 2023 at 06:59 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
lauriiiComment #5
srishtiiee commentedComment #6
lauriiiCan we add some test coverage for this? 😇
Comment #7
berdirthere are a few categories where the current order doesn't really reflect importance. A good example is IMHO Selection list, at least for me, list (text) is the 90%+ use case, rarely list (integer) and I don't think I've ever used list (float) in my life. The current order is the opposite of that. we could use weights to improve that and then a test can assert that list (text) shows up before list (integer)?
kind of same for number, number (integer) is I think also the most common option, but float and decimal line currently nicely have the same height, not sure how that will look then ;)
(the add example for test was actually a crosspost with my comment)
Comment #8
lauriiiI agree that we could use this for re-ordering the selection list options based on what @Berdir is proposing. That seems like a perfect way to show case this feature 👍
Comment #9
srishtiiee commentedNumber field types don't look that bad IMO, will revert the changes if we decide otherwise.
Comment #10
berdirNice. Should decimal be before float given that the description of float says you should probably use decimal?
Comment #11
utkarsh_33 commentedChanges look good to me and also the feedbacks in #7 and #10 are addressed.So marking it as RTBC.
Comment #14
lauriiiCommitted f9b363c and pushed to 11.x. Thanks!