Skip to content
This repository was archived by the owner on Jul 24, 2023. It is now read-only.

Specifics of using gem with bundler #48

Closed
glebe opened this issue Mar 27, 2013 · 3 comments
Closed

Specifics of using gem with bundler #48

glebe opened this issue Mar 27, 2013 · 3 comments

Comments

@glebe
Copy link

glebe commented Mar 27, 2013

When including gem through bundler, one should use the following syntax:

gem "ruby-openid", :require => 'openid'

to avoid problems like this on application start

ActionDispatch::Session::SessionRestoreError (Session contains objects whose class definition isn't available.
Remember to require the classes for all objects kept in the session.
(Original exception: uninitialized constant OpenID [NameError])
):
@danko-master
Copy link

I have a similar problem, after restarting server.

@ignatiusreza
Copy link

any news on this? we also got this on production, having to manually require it is a bit cumbersome

r7kamura added a commit to r7kamura/ruby-openid that referenced this issue Jul 20, 2018
@r7kamura
Add lib/ruby-openid.rb for Bundler.require
fa6b2c6 
To remove extra :require option like this:

```rb
gem "ruby-openid", require: "openid"
```

This change may be related to openid#48.
@r7kamura r7kamura mentioned this issue Jul 20, 2018
Merged
@tobiashm
Copy link
Contributor

Fixed by #112

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@tobiashm @glebe @ignatiusreza @danko-master