Add timezone() Support to Laravel Trend for Custom Timezone Aggregations #76
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This update introduces the
timezone()
method to Laravel Trend, allowing users to specify a custom timezone for date aggregation operations. By setting a timezone, all date-based intervals (perMinute()
,perDay()
, etc.) are adjusted to the specified region, providing accurate data trends for specific time zones. This addition is especially beneficial for applications where data trends need to be localized, such as setting the timezone to "Asia/Dhaka" for users in Bangladesh.Example usage: