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
Copy file name to clipboardExpand all lines: components/dateinput/supported-formats.md
-107Lines changed: 0 additions & 107 deletions
Original file line number
Diff line number
Diff line change
@@ -14,13 +14,10 @@ This article explains the format strings and specifiers supported by the Telerik
14
14
15
15
The `Format` property can take a number of possible format strings, and this is a list of the supported options and their effects.
16
16
17
-
<!-- ## Custom Formats -->
18
-
19
17
The .NET framework supports a list of format specifiers for dates that you can use to build your own format strings: [https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings](https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings). The Telerik Date Input steps on them and carries over as many as possible to the client-side to validate and facilitate user input.
20
18
21
19
>caption Using supported .NET format specifiers to define date format in the Telerik Date Input
22
20
23
-
24
21
````CSHTML
25
22
@using Telerik.Blazor.Components.DateInput
26
23
@@ -63,116 +60,12 @@ The .NET framework supports a list of format specifiers for dates that you can u
63
60
*`z`, `zz`, `zzz` - UTC offsets
64
61
*`K` - kind
65
62
66
-
<!-- `t` and `tt` -makes h and hh useless even though they would maybe work -->
67
-
<!-- `g`, `gg` - maybe should never be supported, since it may not be editable -->
68
-
<!-- `K` - not tested until localization arrives, maybe should never be supported since it is not really an editable portion -->
69
-
<!-- `f` through `ffffff` and `F` through `FFFFFF` have not been tested as they are too granular for the current feature set of the components -->
70
-
71
-
72
-
<!--
73
-
74
-
>caption Most of the available custom format strings in .NET are used in the examples below
75
-
76
-
unsupported ATM:
77
-
78
-
m - single digit minutes
79
-
t and tt - AM/PM indicators -makes h and hh useless even though they would maybe work
80
-
g, gg - epoch indicators - maybe never, since it may not be editable
81
-
ddd, dddd - day names
82
-
z, zz, zzz - UTC offsets
83
-
K - kind - not tested until localization arrives, maybe never will be supported since it is not really an editable portion
The .NET framework also has a list of standard formats for dates: [https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-date-and-time-format-strings](https://docs.microsoft.com/en-us/dotnet/standard/base-types/standard-date-and-time-format-strings). They are **not** supported with the Telerik Date Input for Blazor at this point.
124
65
125
66
>caution While the results of unsupported format specifiers values will render correctly, editing is not supported.
0 commit comments