Downgrade to stack lts-16.12 to support more users

[joel-bach]

• Remove Ord instance requirement of Value by not using it in a set
• Fix printing api key header name as string instead of char list

[NorfairKing]

I certainly appreciate this! Is there anything that could go wrong with these sets becoming lists?

[joel-bach]

I certainly appreciate this! Is there anything that could go wrong with these sets becoming lists?

We have two different cases:

• Enum: No, I do not think that this is gonna break something as the user is responsible to not duplicate entries in the enum field (I do not know any reason why someone would want this).
• oneOf, allOf, anyOf: Here I cannot imagine a problem either but this is somewhat more complicated as the different schemas get fused in the case of allOf. But none of the big OpenAPI 3 specifications we test with had any problems with it so I am quite confident it will not break anything.

In addition we do not mess with the declaration order anymore so enums should appear in the order they were declared, which I like.

[NorfairKing]

Sounds great!

In addition we do not mess with the declaration order anymore so enums should appear in the order they were declared, which I like.

Yes I like that too!