You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So, this will require a significant amount of compile time programming, because we need to deduce the type of the return of the custom function. If the type is nullable then we need to decode the value within the object reading code and determine if the value is null so that we can skip writing out keys.
Because this fix would affect object serialization code, I'm going to spend some time considering this issue and tackle it when I have a good amount of time to determine a flexible solution. So, I would expect it to be a while until this feature is added. But, thanks for bringing this up!
Hello,
I am using custom Lambda to output a field or skip based on a condition, but I found it can't skip the null.
sample code:
Use it:
The output is:
{
"i": 287,
"d": 3.14,
"test": null
}
But I would expect the null can be skipped. Is it to add this feature for custom lambda? thanks!
The text was updated successfully, but these errors were encountered: