@liamnichols

Because useFixWidthIntegers was removed all of the tests need to be updated because its default was true. So, would you like me to either:

1 - update the tests as newly generated with Int32/Int64
Very large diff, but upholds default behavior. Test to be added would be overriding datatypes

2 - update the test definitions with int32/int64 overrides
Smaller diff, but all test datatype overrides. Test to be added would be a plain test for default behavior

Good point! Let's preserve the original behaviour first (use a default of Int for both of the formats) and then we can sort the default later 👍🏼

To accommodate the smallest diff here for "preserving the default behavior" I force int32/int64 to be Int which only requires one test case to be updated but will be removed.

Commented TODO at the top of Generator+DataTypes for next step. Updating the tests will be a big diff also due to us not previously respecting float.

In my documentation I state that types must conform to Codable. I assume this because I think we can make the decision to remove the options skipRedundantProtocols, alwaysIncludeDecodableImplementation, and alwaysIncludeEncodableImplementation unless there is something I am missing that require this behavior.

If there is no other motive for these options, I just think that these are kind of redundant as it's implicitly expected that objects are Decodable+Encodable from/to network calls. Codable conformance is default and can be removed manually if desired as always.