fix duration for workload

[warjiang]

What type of PR is this?
/kind bug

What this PR does / why we need it:
The duration of workload is hard coded in the frontend code, just fix that.
Which issue(s) this PR fixes:
Fixes #169

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

- fix the duration calculation for workload 

[warjiang]

/assign @samzong

[samzong]

The backend usually returns the server time, which should be UTC by default, and it may be necessary to handle the time zone differences; here, is it the browser time being obtained?

[warjiang]

it's a good question 🤔 , and dayjs(which we used in our project) use browser timezone in default, and if the timezone differs from local(here refer our personal computer) and server(which means the karmada-dashboard-api ), the calculation of duration may be wrong

[samzong]

dayjs support plugin utc and timezone.

[warjiang]

dayjs support plugin utc and timezone.

yeah, but that's not key problem, key problem is the difference between client time for different regions. In fact the duration for workload is an absolute number, should be different across regions.

[samzong]

maybe just convert it to the current time zone of the browser.

No need to consider multiple time zones. like this.

import dayjs from 'dayjs';
import utc from 'dayjs/plugin/utc';
import timezone from 'dayjs/plugin/timezone';

dayjs.extend(utc);
dayjs.extend(timezone);

export function calculateDuration(start: string | undefined) {
  if (!start) return '-';
  // Convert UTC server time to browser's local timezone
  const startDate = dayjs.utc(start).local();
  const endDate = dayjs();
  const duration = dayjs.duration(endDate.diff(startDate));
  return duration.humanize();
}

[warjiang]

+1, that's a good idea. Just now I still work on getting timezone from server and set defaut timezone for dayjs in frontend. Converting start(server time) to client time is more simple than what i did just now, great~

[RainbowMango]

I think we can squash the commits before moving this forward.

[warjiang]

I think we can squash the commits before moving this forward.

thanks for your kindlly remind, 😄

[warjiang]

@samzong plz check it again~

[samzong]

great!

[samzong]

/lgtm
/approve

[karmada-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: samzong

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [samzong]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment