More App::Prove::State Questions
publiustemp-tapx at yahoo.com
Sun Aug 24 10:32:43 UTC 2008
Working some more on App::Prove::State and I'm wondering (again) how much of the API I can change and internal structure I can change. These changes will likely break older versions which use state, but I think it's an important change.
For example, currently, 'tests' returns a hashref. I'd like it to return an array of tests in the order they were run (or perhaps in an order specified in the where clause).
For various reasons, this also means restructuring the internal .prove file which is stored. This also means slapping a version on results and if no version is present or if the older version is found, we assume we will be showing the ""No saved state, selection will be empty" message (or a variant explaining that the version is out of date).
I hate changing things too much, but since this won't break the core parser, I think we're fine.
Until I hear otherwise, I'll proceed under these assumptions.
Buy the book - http://www.oreilly.com/catalog/perlhks/
Tech blog - http://use.perl.org/~Ovid/journal/
Twitter - http://twitter.com/OvidPerl
Official Perl 6 Wiki - http://www.perlfoundation.org/perl6
More information about the tapx-dev