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
Customers have huge and complex pipelines. Bond serialization is buried deep in the code, and sporadic errors like a null value in some record may require an humongous amount of time such as connecting to the cloud service for debugging (before getting clearance for doing so), or adding more logs elsewhere (which would be duplicated when Bond is used for logging), and deploying again.
Therefore, this error message is not being helpful at all. It should state at very minimum the field that is not satisfying the condition, and ideally the schema name as well.
The text was updated successfully, but these errors were encountered:
is there a workaround to this. The bigger issue is boolean with false values are also being omitted.
I need all the fields to be present in the serialized json as this will be deserialized in another application based c++ where these fields are not marked as nullable.
@himanshusainig, this issue is specifically about a better error message when a = nothing field is encountered that cannot be serialized. Can you please create a new issue about your problem? It will be useful to see the .bond schemas that each app. Make sure you've tested with the currently released versions of Bond too, in case the issue has been fixed already.
Customers have huge and complex pipelines. Bond serialization is buried deep in the code, and sporadic errors like a null value in some record may require an humongous amount of time such as connecting to the cloud service for debugging (before getting clearance for doing so), or adding more logs elsewhere (which would be duplicated when
Bond
is used for logging), and deploying again.Therefore, this error message is not being helpful at all. It should state at very minimum the field that is not satisfying the condition, and ideally the schema name as well.
The text was updated successfully, but these errors were encountered: