> no exhaustive `switch` This is what linters will do for you by default. > we instead need to create ValidEnumValues and remember to update it every time a n

> no exhaustive `switch` This is what linters will do for you by default. > we instead need to create ValidEnumValues and remember to update it every time a new enum value is added Code generators are first class citizens in go, and writing an icky but reliable test won't be too hard either.