Skip to content


--require option on command line clobbers same in .rspec #594

dchelimsky opened this Issue · 0 comments

2 participants

RSpec member

Given .rspec with --require ./onefile.rb
When I run rspec spec --require ./anotherfile.rb
Then ./anotherfile.rb is requred
But ./onefile.rb is not

The problem is that the collection of requires derived from .rspec is overwritten by those on the command line instead of merged.

@dchelimsky dchelimsky referenced this issue in guard/guard-rspec

rspec ignores -r, --require PATH option #108

@alindeman alindeman was assigned
@alindeman alindeman added a commit that closed this issue
@alindeman alindeman `--require` is merged among different configuration sources
* e.g., `--require` specified in SPEC_OPTS will be merged with
  `--require` specified in `.rspec`
* Fixes #594
@alindeman alindeman closed this in 9518119
@alindeman alindeman added a commit that referenced this issue
@alindeman alindeman Changelog for #594 [ci skip] d89c87b
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.