1.3.0-M1: Improved Errors and User-Facing Messages

This release is in honor of the 1-year anniversary of DazzleConf's first deployment to Maven Central.

Compared to 1.2.0, where much was done, 1.3.0 has far less upheaval. The planned features for 1.3.0 are described by this milestone.

Additions:

• Significantly improved error messages:
  • Messages have been clarified and detail added to them.
  • Examples of correct user input are given.
• Added a few methods accepting CharSequence for exception messages, to reduce boilerplate.

Fixes:

• Null elements are prohibited in lists, sets, collections, and maps. Previously, it was possible in some cases to access these null elements, and, through ValueSerialiser, to deserialize them as some other type. #23
• In previous versions, MissingKeyException was thrown where MissingValueException should have been thrown. This is now corrected.

Migration from 1.2.x:

• Null collection elements are now (correctly) prohibited. If you were accidentally relying on the presence of null collection elements in your ValueSerialiser implementation, your code's behavior may be affected.
• MissingValueException is now correctly thrown in the case where it should be thrown (MissingKeyException used to be thrown instead).