-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor requires #57
Conversation
With the refactoring of spec_helper, a bug like this can now be catched by "bundle exec rspec spec/lib/twingly/url/utilities_spec.rb", but I did not succeed in catching in "bundle exec rake". We can continue to work on that from this. Close #56.
I get the same error when running just the NullURL specs. (it must have access to the URL class here: https://github.com/twingly/twingly-url/blob/master/lib/twingly/url/null_url.rb#L8) This is not a problem in production since you never should require null_url by yourself.
|
I guess we should fix it anyway |
Done in 4172a38 |
👍 |
We seem to use “require_relative” in /lib and “require” in /spec
I think this looks good now |
To catch require bugs like #56.
Travis CI install all gems into vendor/, so we tried to run all sort of specs...
Tested locally, LGTM :) |
Will wait with new version release until we have gotten our other ongoing PRs in |
With the refactoring of spec_helper, a bug like this can now be caught by
but I did not succeed in catching it in
We can continue to work on that from this.
Close #56.