Support sending any base::Value types over mojo |
||
Issue descriptionMojo structs typemapped to base::DictionaryValue and base::ListValue already exist, but to send an arbitrary base::Value requires wrapping it in a ListValue. Additionally, since they map directly to the Value types, they can't be used in sync responses (sync responses require a move assignment operator). std::unique_ptr<base::Value>, std::unique_ptr<base::DictionaryValue> and std::unique_ptr<base::ListValue> should be supported instead.
,
Dec 28 2016
,
Jan 17 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e1b6d38fd369d03ac2f13349a9d329ff0a8943d9 commit e1b6d38fd369d03ac2f13349a9d329ff0a8943d9 Author: sammc <sammc@chromium.org> Date: Tue Jan 17 22:40:01 2017 Change base::DictionaryValue mojo deserialization to not expand paths. Currently, when deserializing a base::DictionaryValue from mojo, the values in the dictionary are set with Set(), which expands paths. This causes data to be mutated when round-tripping through mojo. This CL changes it to use SetWithoutPathExpansion() to avoid this mutation. BUG= 675860 Review-Url: https://codereview.chromium.org/2636113002 Cr-Commit-Position: refs/heads/master@{#444169} [modify] https://crrev.com/e1b6d38fd369d03ac2f13349a9d329ff0a8943d9/mojo/common/common_custom_types_unittest.cc [modify] https://crrev.com/e1b6d38fd369d03ac2f13349a9d329ff0a8943d9/mojo/common/values_struct_traits.cc |
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Dec 21 2016