Naming conflict with RSpec
Reported by Simon Harris | February 15th, 2008 @ 06:18 AM
Ambition::Processors::Base attempts to add context accessors unless a context method has already been defined. Unfortunately, the latest version of rspec somehow manages to add a context method. (I say somehow as it's late and I can't quite work out how even though I know where it's being done.)
A solution seems to be to remove the aliasing of context to describe in module Spec::Extensions::Main.
I wonder if the alias is there for legacy reasons and if we can ask the RSpec guys to remove it.
Comments and changes to this ticket
-
Chris Wanstrath February 16th, 2008 @ 03:45 AM
- → State changed from “new” to “open”
I guess we could call our `context` something else. I suppose test/spec does the same thing, but for some reason it hasn't affected us. Maybe because of the order in which we require stuff.
-
ctran March 31st, 2008 @ 10:07 PM
Any work-around?
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
