Add a weight for the options within a field category

Can we add some test coverage for this? 😇

there 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 ;)

I 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 👍

Number field types don't look that bad IMO, will revert the changes if we decide otherwise.

Nice. Should decimal be before float given that the description of float says you should probably use decimal?

Changes look good to me and also the feedbacks in #7 🐛 Add a weight for the options within a field category Fixed and #10 🐛 Add a weight for the options within a field category Fixed are addressed.So marking it as RTBC.

lauriii → closed merge request !4469

Committed f9b363c and pushed to 11.x. Thanks!

Automatically closed - issue fixed for 2 weeks with no activity.