garrettdimon,

Quick and dirty custom assertion to streamline ensuring valid syntax in generated Ruby files when testing custom generators.

  1. Accounts for destination_root
  2. Runs ruby -c to check a file's syntax
  3. Displays the full path (including destination_root) to the offending file if it fails

It works, but something tells me there's likely a better way to do some or all of this?

  • All
  • Subscribed
  • Moderated
  • Favorites
  • rails
  • DreamBathrooms
  • mdbf
  • ngwrru68w68
  • magazineikmin
  • thenastyranch
  • rosin
  • khanakhh
  • osvaldo12
  • Youngstown
  • slotface
  • Durango
  • kavyap
  • InstantRegret
  • tacticalgear
  • anitta
  • ethstaker
  • provamag3
  • cisconetworking
  • tester
  • GTA5RPClips
  • cubers
  • everett
  • modclub
  • megavids
  • normalnudes
  • Leos
  • JUstTest
  • lostlight
  • All magazines