Re: [rspec-users] why no newlines in failure messages?

2007-09-08 Thread David Chelimsky
On 9/8/07, Jeremy Stell-Smith <[EMAIL PROTECTED]> wrote:
> Instead of :
>
> expected "\n  red\n  blue\n", got "\n
> red\nblue\n  " (using ==)
>
> could we make rspec exceptions look more like :
>
> expected "\n  red\n  blue\n",
>  got "\n  red\nblue\n  " (using ==)

Trunk's already doing this. Not released yet.

>
> or if that is too hard, even :
>
> expected
>  "\n  red\n  blue\n", got
> "\n  red\nblue\n  " (using ==)
>
> then it becomes readily easy to scan the two values and see differences, as
> opposed to (something I have done far too often in the last few months)
> copying the diff, pasting it somewhere and manually doing this.
>
> I have looked at the --diff option, but it doesn't show how something has
> changed, just where it has changed which is not quite what I want.
>
> Jeremy
>
> ___
> rspec-users mailing list
> rspec-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users


[rspec-users] why no newlines in failure messages?

2007-09-08 Thread Jeremy Stell-Smith
Instead of :

expected "\n  red\n  blue\n", got "\n
red\nblue\n  " (using ==)

could we make rspec exceptions look more like :

expected "\n  red\n  blue\n",
 got "\n  red\nblue\n  " (using ==)

or if that is too hard, even :

expected
"\n  red\n  blue\n", got
"\n  red\nblue\n  " (using ==)

then it becomes readily easy to scan the two values and see differences, as
opposed to (something I have done far too often in the last few months)
copying the diff, pasting it somewhere and manually doing this.

I have looked at the --diff option, but it doesn't show how something has
changed, just where it has changed which is not quite what I want.

Jeremy
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users