Open maksar opened 7 years ago
@maksar I suggest you defining Public::ApplicationController as
module Public
class ApplicationController < ::ApplicationController
...
end
end
@flyerhzm That is exactly what I did to fix the error. Further more, I think construct class A < A
should not be used. However, since ruby handles such situation well, probably RBP should too (at least have protection against eternal recursion).
We have such code in our legacy application:
rails_best_practices-1.18.0/lib/rails_best_practices/core/methods.rb:57 #mark_parent_class_method_used method traverses inheritance tree up indefinitely. Ruby and Rails, however, handling situation just fine, assuming, that
Public::ApplicationController
inherits from::ApplicationController