-
Notifications
You must be signed in to change notification settings - Fork 21
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
Timestamp issue? #67
Comments
This was a regression introduced in #40 (extension of changes in #33) It is because of this trait cel-rust/interpreter/src/context.rs Line 50 in 2cb75cb
Which ultimately calls this function, converting the timestamp to a string cel-rust/interpreter/src/ser.rs Line 577 in 2cb75cb
Still thinking about exactly how to solve this. In the meantime, you can use this to add a context.add_variable_from_value("foo", Value::Timestamp(DateTime::default())) |
I need to think through the repercussions of #68 but it does resolve the issue (test added). Because of this addition, I don't think there will be any breaking changes. We were effectively doing that before, just with an unnecessary intermediate serialization step. |
I'm not sure whether I'm the one doing something here, but I find this slightly confusing:
Interestingly, this yields comparing:
Timestamp(2023-05-28T00:00:00+00:00) vs String("2023-05-28T00:00:00+00:00")
Where the lhs is the
timestamp('2023-05-28T00:00:00+00:00'
, but for some reasonts
ends up being a ...String
? Am I missing something here?The text was updated successfully, but these errors were encountered: