-
Hey,
I might be missing an option but in case I'm not, I'd love to be able to change the date format from: mm/dd/yyyy to dd/mm/yyyy as an Australian.
Thanks so much!
-
## Please select if your request is either something new or an enhancement ##
- [x] Enhancement of an existing Feature.
- [ ] Request of a new feature.
## Please select the area your reques…
-
When I initially started Jiff, my plan was always to stick to the Gregorian calendar. And I planned this even though Temporal specifically supports non-Gregorian calendars. Temporal has blazed a trail…
-
Version ` "@js-temporal/polyfill": "0.4.0"`
Just tried: `Temporal.PlainDate.from('2022-W12')`, where `2022-W12` is ISO week-numbering format.
Receiving: `Uncaught RangeError: invalid ISO 8601 stri…
zzal updated
11 months ago
-
@daveajones
As I see the documentation for [value standard](https://github.com/Podcastindex-org/podcast-namespace/blob/main/value/value.md), I stumple over the rather local date format that might ca…
vv01f updated
3 years ago
-
```
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.
…
-
I need to assert the date field body of my api response which is in ISO 8601 format i.e 2016-11-09T16:04:27.964Z
Is there a way I can do so?
-
It would be best if Esri could fix this issue on their side, but might be something that EME for Pro could resolve. When editing metadata in Pro, dates seem to be saved in the OS default syntax (usua…