Wrong alternate file of app/lib/* about rspec.tmbundle HOT 8 CLOSED

Confirmed. For app/lib/foobar.rb, what should the correct alternate file be – spec/app/lib/foobar_spec.rb or spec/lib/foobar_spec.rb?

from rspec.tmbundle.

I just tried this today and app/lib/foobar.rb correctly created the alternate file spec/lib/foobar_spec.rb. Seems good to me!

It definitely shouldn't contain /app/ otherwise we'd expect app/models/foobar.rb to map to no longer map to spec/models/foobar_spec.rb.

from rspec.tmbundle.

Did you try it inside a Rails app?

In Rails apps, lib/foobar.rb is already mapped to spec/foobar_spec.rb, so not sure if we should map app/lib/foobar.rb also to spec/foobar_spec.rb …

from rspec.tmbundle.

It just occured to me that app/lib/foobar.rb should map to spec/models/lib/foobar.rb. Would make sense, wouldn’t it?

from rspec.tmbundle.

Oh I see what you mean now. While I suppose that might be a matter of preference, I can't think of a better option. I also can't imagine a situation in which both app/lib/foobar.rb and app/models/lib/foobar.rb both exist at the same time, so I think your solution makes sense.

from rspec.tmbundle.

Ah, app/lib/foobar.rb vs. app/models/lib/foobar.rb was the case I didn’t think of – but as you say, I think we can ignore that :-)

from rspec.tmbundle.

Other projects like RubyMine simply search all folders for a filename matching the pattern which is super lazy, and doesn't try to create anything. We're already going above and beyond in helpfulness here. If someone has super strange structure they can complain to us, or just navigate back and forth themselves :)

from rspec.tmbundle.

You know that feeling when you look at something you wrote some hours ago and it just doesn’t make sense anymore? app/lib/foobar.rb ↔︎ spec/models/lib doesn’t make sense. I think I’ll go with app/lib/foobar.rb ↔︎ spec/app/lib/foobar.rb – this is at least guaranteed not to collide with anything else.

from rspec.tmbundle.