Parent Directory | Revision Log
Links to HEAD: | (view) (annotate) |
Sticky Revision: |
Frey::Class::Refactor::Modify Frey::ClassLoader -> Frey::Class::Loader
output tests while running them, store output in files with timestamp (to enable regression reporting at one point)
Frey::Test::Runner will now run tests if all classes which are modified on disk
added has_tests which return all tests which use_ok class
rename invocable events with prefix as_ with fallback in Frey::Web This started with brute-force rename using: perl -p -i -n -e 's/sub markup/sub as_markup/' `grep -lr 'sub markup' lib t` perl -p -i -n -e 's/sub data/sub as_data/' `grep -lr 'sub data' lib t` perl -p -i -n -e 's/sub sponge/sub as_sponge/' `grep -lr 'sub sponge' lib t` perl -p -i -n -e 's/->markup/->as_markup/' `grep -lr -- '->markup' lib t` perl -p -i -n -e 's/->data/->as_data/' `grep -lr -- '->data' lib t` perl -p -i -n -e 's/->sponge/->as_sponge/' `grep -lr -- '->sponge' lib t` perl -p -i -n -e 's!/markup!/as_markup!' `grep -lr -- '/markup' lib t etc` perl -p -i -n -e 's!/data!/as_data!' `grep -lr -- '/data' lib t etc` perl -p -i -n -e 's!/sponge!/as_sponge!' `grep -lr -- '/sponge' lib t etc`
decrease output without debug
better error reporting
move form params generation into Frey::Action to share between Frey::Run and Frey::Pipe
tweak various bits on Frey::PPI to wrap find within tree in evals so we can *SEE* errors, and split out includes which can be called externally. Support also values as from type constraints.
collect include from PPI::Statement::Include
implement PPI parser to get default attribute_order
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.
ViewVC Help | |
Powered by ViewVC 1.1.26 |