make type coercion optional

[aschus]

Thanks for the great library!

I'd like to have an option to disable the type coercion add-on. My use case would be to ensure that expressions evaluated using this library in a Python backend always have the same results/errors as when evaluated by the original cel-rust compiled to WebAssembly in the frontend. That way I could use the same expressions both in the backend and in the frontend and could catch any errors already in the backend.

I fear this would probably double the amount of required test cases, so if this is out of scope for you, just ignore this :-)

[hardbyte]

You're most welcome! I agree there’s a need for both strict CEL semantics and possibly better control over how results are returned.

My short term plan is to add an EvaluationMode enum so you can disable all type promotions/re-writes and exactly match cel-rust behavior. I'm thinking about also adding a separate ReturnFormat option to let you skip converting back to Python types when you want to work directly with CEL values.

[hardbyte]

Early draft in #13

[aschus]

Thanks, you're quick!

Looks like a nice solution :-)

[hardbyte]

Merged - will be in the next release.