Yes, it is. We've experimented and had success with jsonutil.Merge as an alternate to jsonpatch for First Party Data. jsonutil.Merge is built on jsoniter taking advantage of that library's callback architecture to customize behavior of ext handling.
It's our intention to replace jsonpatch usage with jsonutil.Merge for a performance increase. Anyone is welcome to put up a PR that beats us to it. :)
No argument against skipping steps which don't apply to everyone. in this case though, how can the default account json ever be nil?
Yes, it is. We've experimented and had success with
jsonutil.Mergeas an alternate tojsonpatchfor First Party Data.jsonutil.Mergeis built onjsonitertaking advantage of that library's callback architecture to customize behavior of ext handling.It's our intention to replace
jsonpatchusage withjsonutil.Mergefor a performance increase. Anyone is welcome to put up a PR that beats us to it. :)No argument against skipping steps which don't apply to everyone. in this case though, how can the default account json ever be nil?