Conflict with closure_tree about wallaby-rails HOT 9 CLOSED

Let me double-check if any Class is still stored in Wallaby::Map. Is this issue for envisage?

from wallaby-rails.

Yeah, this is for Envisage. The develop branch.

from wallaby-rails.

Does wallaby attempt to load classes based on database tables? This may be the issue if so.

from wallaby-rails.

Nope, Wallaby only loads the files under eager_load_paths which is the /app folder, it doesn't read the database tables.

Sure, I will take a look.

from wallaby-rails.

@ryanb I can confirm that this is an issue of closure_tree, not wallaby.

I've tried to taken wallaby out completely from the Gemfile, config/routes.rb, config/initializers/wallaby.rb, and if I made any changes to Objective model and visited GET "/objectives", when Rails reloaded, this warning came up. And if you take a look into the list of constants that Rails maintains by using:

ActiveSupport::Dependencies.autoloaded_constants

You will see that Objective is in the list, but the ObjectiveHierarchy created by closure_tree is not captured by Rails Dependencies. Therefore, on every reload, ObjectiveHierarchy will not be removed by Rails before it gets recreated.

from wallaby-rails.

@tian-im oops, sorry about that. I tried removing wallaby as well and was not able to duplicate the warning. I'll close this ticket.

Thanks for taking the time to look into this.

from wallaby-rails.

No worries :)

from wallaby-rails.

FYI, I posted an issue here on closure_tree: ClosureTree/closure_tree#362

from wallaby-rails.

👌

from wallaby-rails.