The issue comes when you write a migration to a new column. If you write the command to include date scopes at the same time it fails. This is because the date scopes library looks for the column to figure out its type. If the column isn't there, the class cannot be loaded.
Two possible solutions to this:
- Issue a warning when the column cannot be found and don't load the scopes
- Allow the user to specify the date column type and skip the column checking
Technically both are possible, but I'm going to go with the second option for now.
The issue comes when you write a migration to a new column. If you write the command to include date scopes at the same time it fails. This is because the date scopes library looks for the column to figure out its type. If the column isn't there, the class cannot be loaded.
Two possible solutions to this:
Technically both are possible, but I'm going to go with the second option for now.