coder.module kicks ass. I'm starting to use it more and more. However, the *killer* feature would be to have a button at the end of the review for "Generate a patch to correct these problems". Then, coder.module would elevate to godsend status. ;)

anyone up for working on this? think of the 1000s of hours of developer this feature would save...

p.s. As an initial version, a "write copy of corrected code to a tmp location" feature would be nearly as good (maybe even better) and definitely a *lot* easier to get working than having coder.module generate .patch files itself.

Comments

douggreen’s picture

douggreen commented

I agree that this would be a killer feature. The place to start is to look at the review definition files (in the includes directory) and the coder documentation. With some crafty regex replacement, many of the changes could be auto-generated. More complicated changes (think about the new args for url() or the menu-subsystem changes) while require call-backs, but certainly this is do-able.

I've included sun's coder_format in the coder scripts directory. He took a different approach than I did, by actually parsing and re-writing the entire file. I don't think it creates a patch, but I do think it creates new source. It's certainly worth looking at.

douggreen’s picture

douggreen commented
Priority: Critical » Normal

I'm downgrading from critical to normal, but I'm leaving "open," rather than marking as "won't fix. I don't suspect that I'll be getting to this anytime soon (unless there was a significant bounty to do it :)

douggreen’s picture

douggreen commented
Status: Active » Closed (fixed)

I'm doing some ticket triage and closing all open 5.x or moving them to the latest appropriate version. See coder_upgrade project n 7.x by solotandem (now included with coder)