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

Fixes #16431: Explicitly set path of PolicyApi include #203

Merged
merged 1 commit into from Sep 5, 2016

Conversation

ehelms
Copy link
Member

@ehelms ehelms commented Sep 2, 2016

Defining modules with syntax :: has unintended consequences with
respect to how modules are looked up. This explicitly declares the
full path to the PolicyApi module instead of relying on Ruby to
attempt to automatically determine it.

Defining modules with syntax `::` has unintended consequences with
respect to how modules are looked up. This explicitly declares the
full path to the PolicyApi module instead of relying on Ruby to
attempt to automatically determine it.
@shlomizadok
Copy link
Member

shlomizadok commented Sep 2, 2016

This seems to break the controller and Foreman won't start :/

@ehelms
Copy link
Member Author

ehelms commented Sep 3, 2016

This #204 should fix the issue you were seeing with Foreman starting. The two changes were unrelated to each other.

@xprazak2
Copy link
Contributor

xprazak2 commented Sep 5, 2016

@shlomizadok it does not seem to break anything for me, does rebasing of core's develop help?

@shlomizadok shlomizadok merged commit 2744a3e into theforeman:master Sep 5, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
4 participants