Actions
Feature #602
closedenum universals_n by generate_enums.py
Start date:
05/12/2024
Due date:
% Done:
0%
Estimated time:
Description
Generate enum universals_n by generate_enums.py.
Files
Actions
Added by Marko Lindqvist almost 2 years ago. Updated over 1 year ago.
0%
Description
Generate enum universals_n by generate_enums.py.
Files
| 0083-Generate-enum-universals_n-by-generate_enums.py.patch (8.71 KB) 0083-Generate-enum-universals_n-by-generate_enums.py.patch | Marko Lindqvist, 05/12/2024 08:07 PM |
I feel like this (already touching every line of the definition) would be a good opportunity to reorder the enum constants, rather than having them in whatever order they happen to have been made in. Could put them (excluding VUT_NONE) in alphabetical order of enum constant (or of name, if we want Tech to go with TechFlag), and then keep our fingers crossed we always remember to insert new ones in the right spot.
Alina Lenk wrote in #note-2:
would be a good opportunity to reorder the enum constants
True, but even if that is left to future tickets, this already makes the reordering a lot easier to do in those future tickets. I felt that this is step big enough to the right direction (I just wanted them in the .def format somehow, before adding new entries)
Ok to proceed with this as it is? Assuming so, if nobody objects (will still wait at least the normal review period of 36h)
No objection from my end; we'll do the reordering separately.