Skip to content
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

SceneTimeRange: Add weekStart support and make sure fiscalYearMonth is used everywhere #375

Merged
merged 2 commits into from
Sep 29, 2023

Conversation

torkelo
Copy link
Member

@torkelo torkelo commented Sep 29, 2023

  • Adds weekStart support (needed for core dashboards)
  • Make sure we pass fiscalYearMonth everywhere

@torkelo torkelo requested a review from dprokop September 29, 2023 05:57
@torkelo torkelo added minor Increment the minor version when merged patch Increment the patch version when merged and removed minor Increment the minor version when merged labels Sep 29, 2023
@torkelo torkelo changed the title SceneTimeRange: Make sure fiscal year is used when evaluating time range SceneTimeRange: Add weekStart support and make sure fiscalYearMonth is used everywhere Sep 29, 2023
@@ -142,6 +142,8 @@ export interface SceneTimeRangeState extends SceneObjectState {
fiscalYearStartMonth?: number;
value: TimeRange;
timeZone?: TimeZone;
/** weekStart will change the global date locale so having multiple different weekStart values is not supported */
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was going to add a comment about that until I came here :D

@torkelo torkelo added the release Create a release when this pr is merged label Sep 29, 2023
@torkelo torkelo merged commit d69a7b1 into main Sep 29, 2023
@torkelo torkelo deleted the fiscal-year-fix branch September 29, 2023 13:02
@grafanabot
Copy link
Contributor

🚀 PR was released in v1.9.0 🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
patch Increment the patch version when merged release Create a release when this pr is merged released
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants