Type and Null Safety

[MelbourneDeveloper]

The main issue with this library is type safety and null safety. The main aim in forking this is to bring full type safety and null safety to the code. The original code was written at a time when dynamic was more popular, and the static analyzer was not configured to be as strict as it could be. That's why we've added the austerity package to all the packages. austerity turns all the warnings up to errors. This made it easy to fix a tonne of violations with dart fix --apply.

However, there were so many violations left over that it wasn't possible to fix them all right at the start. That's why the analysis configs are set to warning instead of error for some rules

The aim is to gradually fix all these and remove any use of dynamic throughout the library, except for tests and examples. If you understand what these lint rules mean, you could help a lot by fixing these up one by one, and then removing the line in the analyzer config to turn the warnings back to errors.