Closed Armitage35 closed 1 year ago
I don't believe we should do this, as it would be a compatibility breaking change (though I don't disagree it's inconsistent)
I agree, this would cause a bunch of issues when running auctions.
Based on concerns for impacts to machine-readable serializations and compatibility - this is not something being considered for 1.x series releases - but if we ever do a 2.0 and break compatibility anyway, then this (and similar rationalizations) could be considered
A minor inconsistency if you look from the outside is that children and grand children enums always start with a 0 whereas parent start with a 1. This means that the count of digits is not always the same depending on if you are looking to a transit to Government parent category (1-9) vs financial and residential (10-11).
This is a minor issue in edge cases where we are looking at the numbers of digits to determine the venue type. Not critical and certainly has a good reason but strange from the outside.