@scmmishra
#10360 (review)

1. Fixed
2. It is fixed
3. I couldn't bring it to the vue context, the only better way I found was this. Maybe if you implement the script within the vue context.
4. Datepicker has the problem that it does not use the language chosen by the user. It would be possible to use window to set values ​​from within Vue, but in the helper we would have to use setInterval() to update the value inside the helper, since the value does not update itself.
   It would be possible to use MutationObserver(), but this wastes unnecessary resources to update a single value instead of looking at the changes in the entire DOM.

In short it is now working.

I thank.

Hey @KokeroO this looks great

• I couldn't bring it to the vue context, the only better way I found was this. Maybe if you implement the script within the vue context.

For this perhaps, you could make file the following file app/javascript/dashboard/composables/useLocaleFormatter.js

import { useI18n } from 'vue-i18n';
import {
  messageStamp,
  messageTimestamp,
  dynamicTime,
  dateFormat,
  shortTimestamp,
} from 'shared/helpers/timeHelper';

export default function useLocaleFormatter() {
  const { locale } = useI18n();

  const localeDynamicTime = (...args) => dynamicTime(...args, locale.value);
  const localeDateFormat = (...args) => dateFormat(...args, locale.value);
  const localeShortTimestamp = (...args) =>
    shortTimestamp(...args, locale.value);
  const localeMessageStamp = (...args) => messageStamp(...args, locale.value);
  const localeMessageTimestamp = (...args) =>
    messageTimestamp(...args, locale.value);

  return {
    localeDynamicTime,
    localeDateFormat,
    localeShortTimestamp,
    localeMessageStamp,
    localeMessageTimestamp,
  };
}

This can be used anywhere in the setup context as

const { localeDateFormat } = useLocaleFormatter();

@pranavrajs
I have some doubts regarding dateFormat, messageStamp and messageTimestamp.
They confuse me, originally in certain situations they give the same result.
Could you take a look? I could unify them.

I just need to fix timeHelper.js and timeHelper.spec.js.

app/javascript/shared/helpers/specs/timeHelper.spec.js
app/javascript/shared/helpers/timeHelper.js

Could you take a look? I could unify them.

Yeah, seems like they can be combined. Just need to handle the isSameYear case in messageTimestamp. But we can combine dateFormat and messageStamp for sure

Could you take a look? I could unify them.

Yeah, seems like they can be combined. Just need to handle the isSameYear case in messageTimestamp. But we can combine dateFormat and messageStamp for sure

@scmmishra
Thanks for the tips. I was able to implement it and do the best I could. This PR will greatly help other languages ​​and I believe that the dates are now better represented.

1. The language setting that contained the region code after the "-" now actually works.

2. I merged messageStamp with dateFormat, which I found gave the same results on different screens.

3. I renamed messageTimestamp to messageDateFormat to handle date formatting in message bubbles and validate the isSameYear() and isSameDay() methods.
   

@KokeroO this looks great! I'll review this ASAP and let you know

Hey! I see that my issue was mentionned here.
In fact, my issue is about the help center and wasn't really about the agent UI...

@Micorksen The help center will also be covered in this PR.

Hey @pranavrajs @sojan-official, can someone please accept this PR?

🐢 Turtley slow progress alert! This pull request has been idle for over 30 days. Can we please speed things up and either merge it or release it back into the wild?