I think it is fine as is. I just wanted to make sure I got the wording
correct. There are so few directories that its being there is very
noticeable. The only place where I see an issue is with older versions
of RSpec in conjunction with ZenTest's autotest. In RSpec 1.1.5 and
later, the absence or presence of this folder makes no difference.
Instead you use an environment variable to make Autotest run the spec
tests. At least that is how it works for me.
Martin Krauskopf wrote:
> Erno Mononen wrote:
>> Chris Kutler wrote:
>>> The docs say that when you create a new ruby application....
>>>
>>> "If the project’s Ruby Platform has the RSpec gem in its repository,
>>> you also get the RSpec folder."
>>>
>>> I am seeing that I get the RSpec folder regardless whether the RSpec
>>> gem is in the repository.
>>>
>>> I just want to make sure it is ok to remove this sentence because it
>>> is not true.
>>
>> Right, the spec folder is always created for plain Ruby projects (for
>> Rails projects the above is still true). Not sure whether this a bug
>> or feature in the Ruby project generator
>
> Not sure what is better way. Something in between would be the best.
> Since user might later install the RSpec or might switch to another
> platform which has RSpec available. So seemed to me less harmless to
> generate 'spec' directory always, rather then conditionally, based on
> the RSpec gem presence.
>
> Ideas, RFEs, welcomed as always.
>
> m.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
dev-unsubscribe@...
> For additional commands, e-mail:
dev-help@...
>
---------------------------------------------------------------------
To unsubscribe, e-mail:
dev-unsubscribe@...
For additional commands, e-mail:
dev-help@...
