-
Notifications
You must be signed in to change notification settings - Fork 900
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
Add another stub for Entitlement for preventing to load from app folder in migration #7729
Add another stub for Entitlement for preventing to load from app folder in migration #7729
Conversation
Good find @lpichler 👍 |
Wait the reason you added a second entitlement in this order is because On Tuesday, April 5, 2016, Joe Rafaniello [email protected] wrote:
Chris Arcand |
@chrisarcand yes exaclty but this is valid when you are using definition with class has_one :entitlement, :class_name => RemoveMiqUserRoleFromMiqGroups::Entitlement but when you use it in quotes has_one :entitlement, :class_name => 'RemoveMiqUserRoleFromMiqGroups::Entitlement' it seems that is not loading the class 'RemoveMiqUserRoleFromMiqGroups::Entitlement' for this case even when I deleted model (I am not sure what are exact differences in these cases when sql is generated or how impact it has, if any) @jrafanie @Fryguy |
I don't think Entitlement should be defined twice like that. I would think that all :class_name should be strings as that's how we do it in other migrations, and don't have a problem. |
Ooooh I see. My fault entirely. Yes we should be using strings. Aside, I hate these sorts of 'flexibility features' :disappointed_eyes: |
d5fe5ee
to
6b7afbb
Compare
Checked commit lpichler@6b7afbb with ruby 2.2.3, rubocop 0.37.2, and haml-lint 0.16.1 |
ok, strings used, thanks guys 👍 |
👍 |
👌 |
#6739
this change is allowing to use https://github.com/testdouble/good-migrations
and prevents to load Entitlement model from app folder
@jrafanie @Fryguy @chrisarcand