Skip to content
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

Handle Rails module defined without Rails env #613

Merged
merged 3 commits into from
Feb 2, 2017

Conversation

wkrsz
Copy link
Contributor

@wkrsz wkrsz commented Jan 26, 2017

Gems like rails-html-sanitizer open Rails module without
actually requiring Rails. Instead check if Rails.env is defined.

Similar to: rails/activeresource#216

Gems like rails-html-sanitizer open Rails namespace without
requiring Rails. Instead check if Rails.env is defined.

Similar to: rails/activeresource#216
@wkrsz wkrsz changed the title Handle situations when Rails module is defined without env Handle Rails module defined without Rails env Jan 26, 2017
> lib/wicked_pdf.rb:198:5: C: Favor a normal unless-statement over a
> modifier clause in a multiline statement.
@wkrsz
Copy link
Contributor Author

wkrsz commented Jan 26, 2017

Two failures (with rails_edge.gemfile) are unrelated to my changes.

Bundler could not find compatible versions for gem "arel":
  In Gemfile:
    rails was resolved to 5.1.0.alpha, which depends on
      activerecord (= 5.1.0.alpha) was resolved to 5.1.0.alpha, which depends on
        arel (~> 8.0)

@unixmonkey unixmonkey merged commit f41d6c4 into mileszs:master Feb 2, 2017
@unixmonkey
Copy link
Collaborator

Cool. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants