Deal with rspec 3's change to describe :symbol behavior

[myronmarston]

See rspec/rspec-core#1240, rspec/rspec-core#1403 and rspec/rspec-core#1405.

You'll probably have to apply a change similar to what was done to its in 1405.

/cc @palfvin

[palfvin]

Sorry for the delay on this. Should be able to get to it tomorrow.

[palfvin]

@myronmarston Assuming that its should continue to treat a symbol argument as it does a string argument, I can see that I have to coerce the former into the latter before passing it to describe in the implementation, but I'm not understanding how this relates to rspec/rspec-core#1405. Or perhaps I'm not parsing your "You'll probably have to apply a change similar to what was done to its in 1405." comment correctly.

[myronmarston]

I'm not understanding how this relates to rspec/rspec-core#1405. Or perhaps I'm not parsing your "You'll probably have to apply a change similar to what was done to its in 1405." comment correctly.

I was specifically referring to the change to its that was part of that PR:

https://github.com/rspec/rspec-core/pull/1405/files#diff-bfb3a47487070f8b14dd153557ac2d51L491

[palfvin]

Of course. I didn't see the modification in the PR changes when I reviewed them initially, but should have checked the its source. Would have saved us both some time ...