-
I am currently working on a model that takes as input, among other data, a string in **ISO 8601 datetime format**.
This string should be converted into a **(numeric) timestamp** using a _converter_.
…
-
> Yes, indeed. I think the examples need some cleanup in general. I'll create a task for it.
>
> Regarding your migration: have you already seen this page in the documentation?
>
> https://dj-fi…
-
ISO 8601 allows durations and time intervals, maybe we should consider supporting this in arrow via a separate class or some other method.
https://en.wikipedia.org/wiki/ISO_8601#Durations
This i…
-
```
What steps will reproduce the problem?
1.Have an expires value for cookie header in ISO 8601 date format.
2. Http headers suggest only three date formats and ISO is not among them.
3. I don't have…
-
```
What steps will reproduce the problem?
1. Date.parse('1997-07-16T19:20:30+00:00').toISOString() !=
"1997-07-16T10:20:30Z"
2. '+00:00' is not recognized as UTC but as timezone of current machine.
…
-
```
What steps will reproduce the problem?
1. Date.parse('1997-07-16T19:20:30+00:00').toISOString() !=
"1997-07-16T10:20:30Z"
2. '+00:00' is not recognized as UTC but as timezone of current machine.
…
-
```
What steps will reproduce the problem?
1. Date.parse('1997-07-16T19:20:30+00:00').toISOString() !=
"1997-07-16T10:20:30Z"
2. '+00:00' is not recognized as UTC but as timezone of current machine.
…
-
```
What steps will reproduce the problem?
1. Date.parse('1997-07-16T19:20:30+00:00').toISOString() !=
"1997-07-16T10:20:30Z"
2. '+00:00' is not recognized as UTC but as timezone of current machine.
…
-
Hey, it would be cool, if `.format()` could be expanded in such a way that one could add time zones, so that the resulting string would become a ISO 8601 compliant zoned date time like
```
2018-07…
-
```
What steps will reproduce the problem?
1. Date.parse('1997-07-16T19:20:30+00:00').toISOString() !=
"1997-07-16T10:20:30Z"
2. '+00:00' is not recognized as UTC but as timezone of current machine.
…