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
Need to figure out whether an auto-serializer is needed/necessary/should be encouraged for data APIs? If so, look into implementing as a before/after hook.
Also, benchmark WSME to see if it a viable alternative. Con: json-patch support may be wonky?
The text was updated successfully, but these errors were encountered:
There is one question before this: do we support non-UTF-8 JSON? According to rfc4627, UTF-16/32 LE/BE JSON are valid. If we support them, then we need to handle encoding in auto serialization/(denationalization, possibly). I know the requests library does it, FYI.
Need to figure out whether an auto-serializer is needed/necessary/should be encouraged for data APIs? If so, look into implementing as a before/after hook.
Also, benchmark WSME to see if it a viable alternative. Con: json-patch support may be wonky?
The text was updated successfully, but these errors were encountered: