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

Fix bug in Padrino::Mounter.app_constant (#1595) #1610

Merged
merged 1 commit into from Mar 2, 2014

Conversation

tyabe
Copy link
Contributor

@tyabe tyabe commented Feb 28, 2014

If the module with the same name as the application class has already been defined,
Padrino::Mounter.app_constant had returned the very module object.

So I intend not to search towards ancestors with second parameter 'false' in 'const_defined?'.
This code is only valid in the Ruby 1.9 or later.

(see #1595 )

If the module with the same name as the application class has already been defined,
Padrino::Mounter.app_constant had returned the very module object.

So I intend not to search towards ancestors with second parameter 'false' in 'const_defined?'.
This code is only valid in the Ruby 1.9 or later.
@namusyaka
Copy link
Contributor

Thank you so much, looks good.
@pablox-cl Could you please check?

ujifgc added a commit that referenced this pull request Mar 2, 2014
Fix bug in Padrino::Mounter.app_constant, fixes #1595
@ujifgc ujifgc merged commit 9f4cfa7 into padrino:master Mar 2, 2014
@tyabe tyabe deleted the fix_mounter branch March 3, 2014 03:46
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.

None yet

3 participants