Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"ISO String To Timestamp.vi" doesn't support date strings #22

Closed
rockethacker opened this issue Dec 22, 2016 · 3 comments
Closed

"ISO String To Timestamp.vi" doesn't support date strings #22

rockethacker opened this issue Dec 22, 2016 · 3 comments
Labels
Milestone

Comments

@rockethacker
Copy link

Your timestamp serialization/deserialization fucntions mention that they convert "ISO" timestamps, but they only provide partial coverage of the ISO-8601 standard. The 1.1.7.33 release addresses a little more of the spec, but it still isn't enough for my use case (JIRA API) where a date but not a time is provided:

2016-12-22

According to the wikipedia page, this should be valid ISO-8601 https://en.wikipedia.org/wiki/ISO_8601

Optimally, you should use an off the shelf ISO-8601 converter that supports more of the spec, but it doesn't appear that one exists (maybe a good candidate for an OpenG function?).

@drjdpowell
Copy link

Comment: I also have multiple packages that try to use ISO-8601 for timestamps (SQLite Library, for example) and it would be nice if there was a common ISO-8601 parser that we could all use. Currently I just use trial-and-error with a number of common specific formats.

@jimkring
Copy link
Contributor

jimkring commented Sep 19, 2017

For what it's worth @rockethacker @drjdpowell, the JKI EasyXML library has a ISO-8601 converter that seems to work pretty well for the 2016-12-22 string, but not the more complex ones:

vi.lib\addons_JKI Toolkits\EasyXML\JKI_EasyXML.llb\Parse XML dateTime String__JKI EasyXML.vi

jimkring added a commit that referenced this issue Sep 19, 2017
"ISO String To Timestamp.vi" doesn't support date strings #22
jimkring added a commit that referenced this issue Sep 19, 2017
Fix for Issue #22 - Added support for parsing data strings with no time
@jimkring
Copy link
Contributor

I've implemented a fix for supporting date strings without time (e.g. "2016-12-22")

@jimkring jimkring added this to the 2.0 milestone Apr 18, 2024
@jimkring jimkring added the bug label Apr 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants