SerializationContext lacking about serialize.linq HOT 5 CLOSED

Actually, the way I'm solving it now isn't all that bad, I simply use the JsonSerializer Deserialize() method to serialize it as an ExpressionNode and then I call .ToExpression with the actual context. It's more work then needed (and I still need to test it) but it's not as bad as calling .ToExpressioNode().ToExpression(ExpressionContext);

from serialize.linq.

I think it worth a try and may actually be considered as an improvement proposal related to #44

from serialize.linq.

is adding ExpressionContext enough? or am I missing something?

from serialize.linq.

You are not missing anything, just adding that overload is enough. It's nothing major (as I manage to work around it in a nice way due to just beeing able to use the JsonSerializer) but it's a minor change that could add some confinience for others (and myself :-D)

from serialize.linq.

glad, it is so simple ;)

from serialize.linq.