sipcapture / homer-app

HOMER 7.x Front-End and API Server
http://sipcapture.io
GNU Affero General Public License v3.0
207 stars 85 forks source link

date format #481

Closed m-j-b closed 2 years ago

m-j-b commented 2 years ago

The date format on the Widget Result tab is dd/MM/yyyy HH:mm:ss e.g. 07/06/2022 08:47:37 Can this be changed? Ideally I'd like to show milliseconds as well.

widget-result-date-format .

github-actions[bot] commented 2 years ago

Your report is appreciated. Please star this repository to motivate its developers! :star:

AlexeyOplachko commented 2 years ago

@m-j-b We've implemented this feature You need to add Advanced Setting with category system and param dateTimeFormat With this structure for JSON object Every field in custom is optional. Field that you're interested in, based on what you said in this issue, is dateTimeResults Example of all tokens that can be used for formatting: https://momentjs.com/docs/#/parsing/string-format/

{
    "format": "YYYY/MM/DD HH:mm:ss",
    "custom": {
        "dateTimeResults": "YYYY/MM/DD HH:mm:ss",
        "dateTimeTransaction": "YYYY/MM/DD HH:mm:ss",
        "dateTimePreferences": "YYYY/MM/DD HH:mm:ss",
        "dateTimeTransactionSubTypes": {
            "flow": "YYYY/MM/DD HH:mm:ss",
            "recordings": "YYYY/MM/DD HH:mm:ss",
            "messages": {
                "date": "YYYY/MM/DD",
                "time": "HH:mm:ss"
            },
            "media_reports": "YYYY/MM/DD HH:mm:ss",
            "message_content": "YYYY/MM/DD HH:mm:ss"
        }
    }
}

This'll be properly documented at a later point

m-j-b commented 2 years ago

Thanks, that works great:

new_date_format_settings

new_date_format_widget

andr-04 commented 1 year ago

It's very helpful information and should be extracted into Wiki document, like a lot of descriptions to other config settings!

I'm new with Homer and my brain is blowing about the dirty and carelessness documentation… 🤯

lmangani commented 1 year ago

@andr-04

It's very helpful information and should be extracted into Wiki document, like a lot of descriptions to other config settings!

Indeed, and users should be doing so.

I'm new with Homer and my brain is blowing about the dirty and carelessness documentation… 🤯

Classic opensource entitlement. Want great docs? Roll up your sleeves and contribute some.

andr-04 commented 1 year ago

Roll up your sleeves and contribute some.

I can do it one time, but it will not cover tons of other regular questions.

Why you as developers, for example @m-j-b in this issue, gives answers here instead of putting them to Wiki at least and leaving here the link to the Wiki? It's a really simple approach, but much more helpful and makes care of users and community overall. It's absurd to turn solved issues into a store room of knowledge.

lmangani commented 1 year ago

I can do it one time, but it will not cover tons of other regular questions.

If everyone covered their own question, we would have 100s of up to date documentation pages on the wiki. But most people come demand what they want when they need it but are not willing to help the next guy by improving documentation. This is opensource, and It's up to users to break this selfish cycle.