Just an FYI: I've uploaded new versions of both Test::JSON and Test::Aggregate. The former has no functional changes, but it works with both the new and old JSON interfaces. Test::Aggregate, on the other hand, has many new features and a brand new interface (the code is prominently labeled as Alpha, so I'm not too worried about this).
I also have a new version of Class::CGI on my hard drive. It passes all of the tests, but I need to finish the documentation. It now delegates to CGI::Simple instead of inheriting from it. Also, CGI::Simple is now optional. It will fall back on CGI if the former is not found. Plus, since I now use delegation instead of inheritance, you can use any code you want for handling form data and query parameters (Apache::Request, anyone?) This is the main thing this module needs to make it ready for production use.
Why not make Test::JSON use JSON::Any? Then you wouldn't have to worry about compat issues. It would also make it easier for people using JSON::Any to test their stuff with Test::JSON since JSON::Any would certainly choose the same JSON module. I know I have had to jump through hoops in the past to get Test::JSON and my JSON::Any based code to play well.
Anyway, just a thought.
- Stevan
Re:Test::JSON should use JSON::Any
Ovid on 2007-12-29T18:17:48
You know, that sounds like a good thought. Looking into now (and I'm already getting plenty of test failures on the new upload, so JSON::Any is looking more appealing).
Re:Test::JSON should use JSON::Any
Ovid on 2007-12-29T18:39:37
Done. Look for version 0.06. Thanks for the suggestion.
