-
Notifications
You must be signed in to change notification settings - Fork 30
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
Feature request: Asterisk in WMIDateTime support #107
Comments
Hi @ThalusA 👋 Can you provide a failing example? I think it should be possible to support this by adding new |
The failing example is 20210601114102.********** |
Can you give an example where you are using this pattern? |
A proprietary software I use that return to me those values, and based on the WMI specification it tells me that it should be accepted as a valid value. |
Reading the spec, I think it might be hard even to represent the simpler "range" variant (the "April 1st any year" example seems complex and doesn't have any Rust analog I can think of). Since even the timezone can be optional, something like Since your example doesn't seem to be valid according to the spec (there should be a If you think the impl is general enough, I'd be happy to accept a PR 😄 |
Understandable, I thought the same thing but I wasn't 100% sure. I might make a PR if I have time in my time-off, for now I just implemented a function to act as the deserializer that deserialize as a string, replace asterisks to zero and then parse it as WMIDateTime |
Hi, based on the WMI specification https://learn.microsoft.com/en-us/windows/win32/wmisdk/cim-datetime, datetime can use asterisk for unspecified value, would it be possible to treat them as 0 or maybe add something that can handle that ? As of right now it can't handle that.
The text was updated successfully, but these errors were encountered: