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
Use implication for skip_active_record/skip_solid (rails#52802)
* Generator options should default to nil for unset
The generator options are effectively tri-state, with true/false meaning
set by the user and nil being unset. However, some of these options were
defaulting to false, meaning they were being treated as set to false by
the user.
This commit fixes this issue by setting the values to nil by default
instead of false so that they are properly "unset" by user.
* Use implication for skip_active_record/skip_solid
When skip_solid was added, it used the "old style" option implication
where skip_*? methods delegate to all the options that should be
implied. This has a few downsides such as making it unclear to users
when conflicting options may be specified (for example,
skip_active_record and no_skip_solid).
This commit changes the skip_solid option to use the new style of
implication so that error messages are better and the predicate method
is simpler.
Co-authored-by: Jon Rowe <[email protected]>
---------
Co-authored-by: Jon Rowe <[email protected]>
0 commit comments