You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I run the autocorrect for RSpec/StringAsInstanceDoubleConstant, it just changes the string to a constant. However, this constant doesn't exist. It would be better to just say it's not autocorrectable, or just make it a double (not instance_double)
As you point out, if the constant is fake, the correction should be to use double.
Do you have issues with the other cop?
We were discussing the removal of “string” as a valid enforced style. Do you happen to use it? Would you agree to this?
My major concern is that it's not auto-correctable. I don't think even unsafe autocorrect should be attempted. I do think prohibiting any non-constant should be flagged on instance_double though.
When I run the autocorrect for
RSpec/StringAsInstanceDoubleConstant
, it just changes the string to a constant. However, this constant doesn't exist. It would be better to just say it's not autocorrectable, or just make it adouble
(notinstance_double
)The text was updated successfully, but these errors were encountered: