-
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
Error: primary::SchemaMigration is not a valid Class name. #186
Comments
Yeah, I saw this error as well. It should be a fake class that comes from Rails test, but I'm not sure how it gets into the environment. The reason it shows up is that Wallaby will go through every ActiveRecord class and associate it with a mode so that Wallaby knows how to handle it when building the Wallaby::Map. But yeah, I think it's safe to ignore it until Rails team fixes it. |
Is there an active issue for this on the Rails repo? The closest thing I could find is this issue: rails/rails#36757 However this doesn't look like something they plan to fix. Can you add an exception in Wallaby to ignore that class name? |
Sure thing |
@ryanb could you update to wallaby 6.1.3 and see if it is ok for you? |
Fixed, thanks! |
I see this error in the log when running Wallaby 6.1.2:
Is it trying to find a model class for every table? Rails manages this table I think.
The text was updated successfully, but these errors were encountered: