I’m working on implementing expectation matchers in rspec, so instead of
this:
cat.should_eat “tuna”
you would write this:
cat.should eat “tuna”
Now the rub is that this generates “warning: parenthesize argument(s)
for future version”. The thing is that, in this case, we know with
some certainty that everything after “eat” is an argument to “eat”,
and that the result of “eat” is an argument to “should”.
I’d like the ability to be able to tell the interpreter that this is
intentional and to not warn in this case, and I don’t want to
accomplish this by turning off all warnings. Is this doable? Does this
strike anybody as nuts? If so, please explain.
The reason I want to do this is that I’ve run this new syntax by a few
people. Those who write a lot of ruby (not necessarily rails) are
perfectly happy writing it like this:
cat.should eat(“tuna”) #produces no warning
But, those who write a lot of ruby on rails, not so much. The parens
are not railsy.
In the end, using matchers is a much more flexible and maintainable
approach to expectations, so it’s likely that it will become “the
way”. The question is whether we can keep all the rails developers who
are already using rspec happy without having to maintain two methods
to achieve the same goal.
Now the rub is that this generates “warning: parenthesize argument(s)
for future version”. The thing is that, in this case, we know with
some certainty that everything after “eat” is an argument to “eat”,
and that the result of “eat” is an argument to “should”.
It used not to warn in Ruby 1.6.4, by the way. I also experienced the
same problem when moving to Ruby 1.8.2 in my package manager facility
(TSC Package manager (TPM) download | SourceForge.net) that I am going to release soon (after
almost 3 years of active development and use in a number of commercial
projects). I have a Ruby-based DSL there for package description, that
used to have statements like these:
generate as ‘bin/act’, source program “project/act.rb”
install into ‘lib/test/accept’, source ruby ‘project’ =>
‘test/accept/action.rb’
Then should can just call have_tag with all the given arguments?
That idea came up a long time ago on the rspec list and got a pretty
quick thumbs down. It does seem to simplify things from a maintenance
perspective, but no more so than this:
intentional and to not warn in this case, and I don’t want to
are not railsy.
without recompiling Ruby.
Anyone who can’t handle some parentheses occasionally shouldn’t be a
Is now the appropriate time for me to re-suggest: @hotel.should.be_booked_solid_on “12/31/2007”
YES!!!
Inspired by your question, I played around for a minute w/ a means of
supporting all three sets of syntax w/ one set of matchers. The result
is not complete yet, but right now the trunk supports all of these
forms for some of the expections:
When I’m done, you’ll be able to use most of the expectations with any
of the three forms, though using the “_” or “.” forms for custom
expectations will require monkey patching an RSpec class, so it will
be an “at your own risk” sort of scenario.
forms for some of the expections:
Thanks for bringing this up Wilson!
Cheers,
David
You may have missed it, but it was exactly what I have suggested (or
imlied to suggest) in my first reply to you
Ah - I did miss it.
What Wilson is talking about has a bit more context. We’ve been
through a number of variations of rspec syntax. everything.with.dots
was one, everything_with_underscores was another, and we’ve even had
some.dots.and.some_underscores.
Wilson was suggesting that we return to a previous version of the
syntax where the receive.and.should get dots but
everything_after_should gets underscores.
Regardless, thanks for the suggestion (or implication thereof).
Now the rub is that this generates "warning: parenthesize argument(s)
people. Those who write a lot of ruby (not necessarily rails) are
are already using rspec happy without having to maintain two methods
to achieve the same goal.
Unfortunately this happens in parse.y, without any conditional code
around it. To my knowledge, there is no way to disable the warning
without recompiling Ruby.
strike anybody as nuts? If so, please explain.
In the end, using matchers is a much more flexible and maintainable
Bummer. Well, you’re a rails developer - how much would this syntax
That being said… why wouldn’t that just be: should_have_tag ?
I haven’t seen anything about this change on the mailing list.
–Wilson.
Remember the whole sugar causes cancer thing? I’ve added suppport for
expectation matchers in part to solve that problem. You can read about
it here:
The reason I want to do this is that I’ve run this new syntax by a few
way". The question is whether we can keep all the rails developers who
are already using rspec happy without having to maintain two methods
to achieve the same goal.
Unfortunately this happens in parse.y, without any conditional code
around it. To my knowledge, there is no way to disable the warning
without recompiling Ruby.
Bummer. Well, you’re a rails developer - how much would this syntax
bug you (in this case a new assert_select wrapper)?
