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
Some SDKs may allow users to include arbitrary data inside context properties. SDKs should only accept strings but we know that's not always the case. Edge should gracefully handle this situation and don't fail, which is the current behavior.
This PR shows one simple example, where adding an integer breaks the behavior of a test: #514
Additionally to integers properties should allow complex objects
Background
No response
Solution suggestions
Just ignoring fields that don't comply with the expected schema should work. Then SDKs should be fixed to send the data properly.
In some situations, like handling integer, it might be possible to do a simple transformation to string, but most of other types will not be that trivial.
The text was updated successfully, but these errors were encountered:
Describe the feature request
Some SDKs may allow users to include arbitrary data inside context properties. SDKs should only accept strings but we know that's not always the case. Edge should gracefully handle this situation and don't fail, which is the current behavior.
This PR shows one simple example, where adding an integer breaks the behavior of a test: #514
Additionally to integers properties should allow complex objects
Background
No response
Solution suggestions
Just ignoring fields that don't comply with the expected schema should work. Then SDKs should be fixed to send the data properly.
In some situations, like handling integer, it might be possible to do a simple transformation to string, but most of other types will not be that trivial.
The text was updated successfully, but these errors were encountered: