The biggest change in this release is enforcing non-nullable constructor values for required ATObject values. While they would normally fail on deserialization/serialization, due to the JsonRequired header for System.Text.Json, it also forced the underlying objects to also be nullable, even though they really need to be set according to the lexicon.
I tried updating with the alpha 3.4 against DarkSky to validate how much this would break things, and the resulting changes seemed to be minor and within reason. I am flexible with changes to this though so if anyone wants to push back, feel free to leave an issue or PR with how you think it should be handled.
What's Changed
- Use full namespace path for Lexicon values by @drasticactions in #161
- Generate required properties as non-nullable by @alnkesq in #160
- Fix incorrect deserialization of CBOR CIDs by @alnkesq in #163
Full Changelog: 3.2.2...3.3.1
Contributors
drasticactions and alnkesq