search for: mrloz

Hi Folks, There is much discussion where I work at present regarding migrations, and the ''correct'' usage or not of them. TL;DR Should migrations be used just to modify schema, and other ''deploy'' tasks done other ways? If yes, how to ensure no repeat runs of such tasks (seeds, jobs etc) Background Once you''re live there are often additional things

My friend Ben Willis and I have developed a gem for the versioning of Rails views. https://github.com/bwillis/versioncake The versioning is done by the naming convention. Image the following series of files : show.v3.json.jbuilder show.v2.json.jbuilder show.v1.json.jbuilder create.v2.json.jbuilder create.v1.json.jbuilder The developer pre-defines all view versions in their config. When a

I recently did some work around some bugs in the generated files within the 3-1-stable branch. I couldn''t see a way to construct a test to reproduce the issue, and the changes were happily accepted. What I am wondering is are there any mechanisms within rails (or a support gem) which can enable full testing of the gem as it would be used (an integration test of sorts). If no such thing