-
-
Notifications
You must be signed in to change notification settings - Fork 21
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
Set future date for timestamp flags #22
Comments
The main issues are: More complex queriesChecks for dates instead of Before: $builder->whereNotNull('accepted_at'); After: return $builder->where('accepted_at', '<=', Carbon::now()); Not all applications or models need such functionalityThis could be solved by adding additional methods to check if this functionality is required. Each flag should has +1 method. Scopes namingFor the flag |
This could be useful for example when you want an article to be automatically shown in future date.
Right now if future
published_at
will be setted - this record will be published immediately. Global scopes and helpers should check not for the null value, but for the exact date is past.This use case will be useful for all timestamp flags. For example
expired_at
flag will be useful for subscriptions and so on.The text was updated successfully, but these errors were encountered: