We are currently introducing DBIx::Class in our team and we would like to start out with DBIx::Class::Schema::Loader. However, we have hard requirements on code style, i.e. we've got Perl::Tidy as part of our pre-commit script, since we haven't had any generated code before. Now, we'd have to make sure that the code that Schema::Loader generates is clean and tidy. We can't run perltidy over the code before commit, since it screws up DBIC's MD5 hashing. So a post-processor integrated into Schema::Loader would be my preferred and probably the only feasible solution. But still: how would you handle this problem?
EDIT I might as well patch DBIx::Class::Schema::Loader::Base to use a perltidypreprocess parameter if it gets one.
0.05000 has been released (previously the development version) it has the overwrite_modifications option rbuels added.
I will try to add a post_process option as well soon.