#191 Naming conflict with RSpec - Plugins

Type	To find
responsible:me	tickets assigned to you
tagged:"@high"	tickets tagged @high
milestone:next	tickets in the upcoming milestone
state:invalid	tickets with the state invalid
created:"last week"	tickets created last week
sort:number, importance, updated	tickets sorted by #, importance or updated
Combine keywords for powerful searching.
Use advanced searching »

#191 open

Naming conflict with RSpec

Reported by ronin-13570 (at lighthouseapp) | 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.
You flagged this item as spam.
ctran March 31st, 2008 @ 10:07 PM
Any work-around?

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.