Comments for Coding Daily

Comment on Write your own custom RSpec formatter by Brian Jones

Brian Jones — Sat, 27 Apr 2013 00:54:20 +0000

Sorry I should have mentioned how to run rspec and use it.

rspec -I my_rspec_formatter/lib -f MyRSpecFormatter

Comment on Write your own custom RSpec formatter by Josh

Josh — Mon, 22 Apr 2013 19:33:51 +0000

This is interesting, but where do I put this code?

Comment on Rails + Devise and Rspec by Cant sign in user in Rspec test ( devise gem )

Cant sign in user in Rspec test ( devise gem ) — Wed, 20 Mar 2013 00:26:21 +0000

[...] also tried this link – http://codingdaily.wordpress.com/2011/09/13/rails-devise-and-rspec/. [...]

Comment on Ruby’s Singleton and Custom Rails Application Configuration by Robert Reiz

Robert Reiz — Sat, 16 Jun 2012 10:02:19 +0000

Thanks for the article. That helped me a lot.

Comment on Test a gem with the Rails 3 stack by Matheus Santana

Matheus Santana — Sat, 16 Jun 2012 01:46:23 +0000

Thanks a lot!

It’s really worthy!

Comment on How to edit ~/.MacOSX/environment.plist from a shell by Eli

Eli — Thu, 14 Jun 2012 13:46:09 +0000

thanks for the post. Helpful info.

Comment on How to test a gem that changes ActiveRecord by Brian Jones

Brian Jones — Mon, 05 Mar 2012 02:22:55 +0000

The file itself is created by sqlite. The directory is probably not automatically created, just need to add a Dir.mkdir to the spec_helper.

Comment on How to test a gem that changes ActiveRecord by Matt Huggins

Matt Huggins — Sat, 03 Mar 2012 22:03:17 +0000

I see you reference db/safeattributes.db, but I don’t see that file anywhere in your codebase. How do you go about creating that file? Do you have to do it manually before the tests can run, and if so, what’s the process?

Comment on Better legacy database support for Rails by Jaime Bellmyer

Jaime Bellmyer — Fri, 28 Jan 2011 18:07:20 +0000

Great article, Bryan! I expanded on your post in my own blog (giving you credit, of course), with example code and a downloadable sample app: Legacy Database Column Names in Rails 3 More importantly, thank you for digging in and creating a nice solution to this problem. I'm sure it'll help a lot of people, and might be worth submitting to the rails core itself.

Comment on Better legacy database support for Rails by Legacy Column Names in Rails 3 « Kansas City on Rails

Legacy Column Names in Rails 3 « Kansas City on Rails — Fri, 28 Jan 2011 16:38:14 +0000

[...] wife/girlfriend, you’re not going anywhere until this issue is resolved. Luckily, Brian Jones has solved this problem for us with his gem safe_attributes. Rails automatically creates accessors [...]