-
This would help with interoperability as ISO 8601 support is provided out of the box in at least [Python](https://docs.python.org/2/library/datetime.html#datetime.datetime.isoformat), [Ruby](http://ru…
-
### Context
xo-server 5.11.3
xo-web 5.11.0
### Expected behavior
Show time in 24h format, e.g.
14:05:23
### Current behavior
Time is displayed in american style like "10 am"
![i…
ghost updated
2 years ago
-
## Parent issue
- #5678
## Failing tests
None. Discovered accidentally.
## Notes
Add a new test to `org.drools.drl.parser.antlr4.MiscDRLParserTest`. Related to #5937. Two options:
- Develop…
-
I had to modify the code in the deserializer.py on line 216, as the api is returning the datetime in the ISO 8601 format, it seemed to only work when I convert the date into the RFC 3339, so including…
-
What's the correct way to parse a ISO 8601 / RFC 3339 datetime string?
This is very common in json communication.
On the server side we are using Rust for our API and [DateTime::to_rfc3339()](https:…
-
eg:
2008
We'd like to use this format for all years. Not currently in kitchen sink XML except for references that require a and b in year field.
-
**The issue occurs while working with:** (check one with "x")
- [ ] *app.storyblok.com (CMS - Interface)*
- [x] *api.storyblok.com (CMS - Content Delivery API)*
- [ ] *mapi.storyblok.com (CMS…
-
# Problem solved by the feature
The current default `java.util.Date` serialization uses `DateFormat.getDateTimeInstance(DateFormat.DEFAULT, DateFormat.DEFAULT, Locale.US)` ([source line](https://gith…
-
### Description
Currently, DateTimeFormatter treats Y and y the same.
Strictly speaking, this is incorrect because Y should only be used for week year format. (see https://errorprone.info/bugpatte…
-
Hi!
[version 1.0.0-1 (Debian).]
These variants of ISO-8601 (as produced by coreutil's `date`) for some reason don't parse:
`python3 -c "import dateparser; print(dateparser.parse('$(date --iso…