-
Notifications
You must be signed in to change notification settings - Fork 12
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
Conflict with closure_tree #189
Comments
Let me double-check if any Class is still stored in |
Yeah, this is for Envisage. The develop branch. |
Does wallaby attempt to load classes based on database tables? This may be the issue if so. |
Nope, Wallaby only loads the files under Sure, I will take a look. |
@ryanb I can confirm that this is an issue of I've tried to taken wallaby out completely from the
You will see that |
@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. |
No worries :) |
FYI, I posted an issue here on closure_tree: ClosureTree/closure_tree#362 |
👌 |
I'm seeing this in our development log:
It appears Wallaby is loading these classes which closure_tree doesn't expect. I tried adding the classes to Wallaby's
exclude
config but I still see these warnings. Can you make it so excluding models makes it so Wallaby doesn't attempt to require them?The text was updated successfully, but these errors were encountered: