On Wed, Nov 12, 2008 at 8:59 AM, David Chelimsky [EMAIL PROTECTED] wrote:
On Wed, Nov 12, 2008 at 7:30 AM, aslak hellesoy
[EMAIL PROTECTED] wrote:
World do
world = Object.new
world.extend(Logging::Logger)
world
end
World do
returning Cucumber::Rails::World do |world|
On 13 Nov 2008, at 15:01, David Chelimsky wrote:
On Thu, Nov 13, 2008 at 8:59 AM, Peter Jaros
[EMAIL PROTECTED] wrote:
On Wed, Nov 12, 2008 at 8:59 AM, David Chelimsky [EMAIL PROTECTED]
wrote:
On Wed, Nov 12, 2008 at 7:30 AM, aslak hellesoy
[EMAIL PROTECTED] wrote:
World do
world =
On Thu, Nov 13, 2008 at 3:59 PM, Peter Jaros [EMAIL PROTECTED] wrote:
On Wed, Nov 12, 2008 at 8:59 AM, David Chelimsky [EMAIL PROTECTED] wrote:
On Wed, Nov 12, 2008 at 7:30 AM, aslak hellesoy
[EMAIL PROTECTED] wrote:
World do
world = Object.new
world.extend(Logging::Logger)
world
end
On Thu, Nov 13, 2008 at 10:01 AM, David Chelimsky [EMAIL PROTECTED] wrote:
That's a cool idea - can you put a feature request in lighthouse?
Done:
http://rspec.lighthouseapp.com/projects/16211-cucumber/tickets/87-yield-existing-world-object-to-world-block
Peter
My use case is that I want to be able to use a Logging::Logger[1]
within my scenario code.
I can create the logger explicitly within the step block, but this is
a hackaround.
I think I could monkey-patch Cucumber::Rails::World to include my
logger, but that also feels dirty.
Is there a
On Wed, Nov 12, 2008 at 2:12 PM, Matt Wynne [EMAIL PROTECTED] wrote:
My use case is that I want to be able to use a Logging::Logger[1] within my
scenario code.
I can create the logger explicitly within the step block, but this is a
hackaround.
I think I could monkey-patch
On Wed, Nov 12, 2008 at 7:30 AM, aslak hellesoy
[EMAIL PROTECTED] wrote:
On Wed, Nov 12, 2008 at 2:12 PM, Matt Wynne [EMAIL PROTECTED] wrote:
My use case is that I want to be able to use a Logging::Logger[1] within my
scenario code.
I can create the logger explicitly within the step block,
