-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[pdata] Deprecate map.Upsert/Update #5975
Conversation
Codecov ReportBase: 92.14% // Head: 92.16% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #5975 +/- ##
==========================================
+ Coverage 92.14% 92.16% +0.01%
==========================================
Files 210 210
Lines 13235 13266 +31
==========================================
+ Hits 12196 12227 +31
Misses 822 822
Partials 217 217
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
47b4ce7
to
38c74ea
Compare
38c74ea
to
c706ada
Compare
c706ada
to
7471208
Compare
7471208
to
358cd50
Compare
251aa01
to
3f8ca9b
Compare
3f8ca9b
to
3becb11
Compare
3becb11
to
b3c473c
Compare
pcommon.Map.Insert/Update/Upsert
methods are the only methods allowing setting the mutable types on the Map. This goes against the established practice of building pdata.This PR add extra methods to
pcommon.Value
andpcommon.Map
to replacepcommon.Map.Insert/Update/Upsert
methods. Deprecation ofpcommon.Map.Insert
is delayed since they are used in many places in contrib. So we want to replaces them first.Updates: #5974 and #5973