Skip to content

Conversation

@tylercallahan
Copy link

This adds a :scopes option to boolean_timestamps that allows the user to skip generating the scope. This may be desirable in particular when the generated scope conflicts with an existing Rails method.

For example, boolean_timestamps :loaded_at attempts to create a scope :loaded and raises an error because the method :loaded is already defined. Adding the scopes: false option avoids the error.

Fixes #7

This adds a `:scopes` option to `boolean_timestamps` that allows the
user to skip generating the scope. This may be desirable in particular
when the generated scope conflicts with an existing Rails method.

For example, `boolean_timestamps :loaded_at` attempts to create a scope
`:loaded` and raises an error because the method `:loaded` is already
defined. Adding the `scopes: false` option avoids the error.

Fixes betterup#7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Automatic scope definition can break applications because of naming issues

1 participant