-
Notifications
You must be signed in to change notification settings - Fork 4.3k
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
Handle client count timezone #15167
Handle client count timezone #15167
Conversation
- Backend convert the timezone to UTC, to mitigate it's impact sending start and end date other than 1. Chose 10 and 20 randomly.
} | ||
if (end_time) { | ||
if (Array.isArray(end_time)) { | ||
let endYear = Number(end_time[0]); | ||
let endMonth = Number(end_time[1]); | ||
end_time = formatRFC3339(new Date(endYear, endMonth)); | ||
end_time = formatRFC3339(new Date(endYear, endMonth, 20)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When testing did the API always return with the last day of the month? Might be worth having backend take a look (or maybe you already have) to see if sending an arbitrary middle of the month day has any implications we're unaware of.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think my original question still applies here - I think a backend dev reviewing would be helpful! Just to make sure this won't introduce anything unexpected. Otherwise thanks for tackling! Nice to have this finally merged :)
Yes, confirmed with backend that they have startOfMonth, endOfMonth for start and end params. I tested it as well. 👍 |
Client count went through major refactoring in 1.10 and as a result straightforward backport was not possible.
* This is the backport for #15167 Client count went through major refactoring in 1.10 and as a result straightforward backport was not possible. * Added changelog * Fix test
* Handle client count timezone - Backend convert the timezone to UTC, to mitigate it's impact sending start and end date other than 1. Chose 10 and 20 randomly. * Added changelog
start and end date other than 1. Chose 10 and 20 randomly.