You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe
Wave supports time data type in ui.table component and it converts timestamp based on internationalisation. (User's local browser time format).
MLOps Wave app shows time and date in different components (ui.markup, ui.text) other than in ui.tables. Therefore it's better to have time data type to use with other wave components like ui.markup and ui.text. This is better for the consistency of the Wave API as well.
Describe the solution you'd like
Introduce time data type to use with ui.markup and ui.text components.
Describe alternatives you've considered
Alternative would be to get local browser time format from JS and use it in other components. But then its inconsistent with ui.table's mechanism.
Introduce time data type to use with ui.markup and ui.text components.
How do you envision this to work?
The proper, simplest and fastest way to do this is to get the browser locale, format your timestamps in python and render them wherever needed, be it ui.markup or ui.text.
I would expect this to work similarly to how i18n works with wave stat cards. @mturoci is that already supported by the framework? If that is supported by the framework then only we can say that wave supports i18n completely.
I would expect this to work similarly to how i18n works with wave stat cards.
Format expressions do not allow arbitrary strings like Current date =${{intl foo minimum_fraction_digits=2 maximum_fraction_digits=2}} only =${{intl foo minimum_fraction_digits=2 maximum_fraction_digits=2}}. Another problem is that ui.text doesn't support data buffers and even if it did, the API would look like:
Is your feature request related to a problem? Please describe
time
data type inui.table
component and it converts timestamp based on internationalisation. (User's local browser time format).ui.markup
,ui.text
) other than inui.tables
. Therefore it's better to havetime
data type to use with other wave components likeui.markup
andui.text
. This is better for the consistency of the Wave API as well.Describe the solution you'd like
Introduce
time
data type to use withui.markup
andui.text
components.Describe alternatives you've considered
Alternative would be to get local browser time format from JS and use it in other components. But then its inconsistent with
ui.table
's mechanism.CC @shereezhang @dulajra @ShehanIshanka
The text was updated successfully, but these errors were encountered: