You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working in a rails codebase that makes use of all three of the request spec directory locations for different reasons needs. Those being spec/requests, spec/api and spec/integration
Would it be reasonable to encode these defaults into the vim-rails plugin? I see spec/integration is present in most places that spec/requests is, but spec/api doesn't appear at all.
I took an early stab at this on my own (https://github.com/phantomwhale/vim-rails) but clearly my blind copy/pasting didn't quite have the desired effect (e.g. the alternative file for spec/api/users_spec.rb is app/api/users.rb instead of app/controllers/users_controller.rb)
The text was updated successfully, but these errors were encountered:
I am aware that the rails-projections feature can probably get my setup working as intended, but given this is the core rspec rails configuration, this issue is to discuss if it's reasonable to have full support for these directories in the vim-rails plugin out of the box
I'm working in a rails codebase that makes use of all three of the request spec directory locations for different reasons needs. Those being
spec/requests
,spec/api
andspec/integration
(Ref: https://github.com/rspec/rspec-rails/blob/8c17b4e5020a4d264e8a79e294c58b5c1ef2b005/lib/rspec/rails/configuration.rb#L36)
Would it be reasonable to encode these defaults into the vim-rails plugin? I see
spec/integration
is present in most places thatspec/requests
is, butspec/api
doesn't appear at all.I took an early stab at this on my own (https://github.com/phantomwhale/vim-rails) but clearly my blind copy/pasting didn't quite have the desired effect (e.g. the alternative file for
spec/api/users_spec.rb
isapp/api/users.rb
instead ofapp/controllers/users_controller.rb
)The text was updated successfully, but these errors were encountered: