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
Fix initialValue JSON expectations in ObjectCreationHelpersTests
Update test expectations to match the unwrapped initialValue format
from 95bf7c6. The initialValue JSON string should contain the
CounterCreate/MapCreate object directly (e.g. {"count": 10.5}),
not wrapped in a type key (e.g. {"counterCreate": {"count": 10.5}}).
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
// Check that the initial value JSON is correctly populated on the mapCreateWithObjectId.initialValue property per RTO11f12, using the RTO11f4 partial ObjectOperation and correctly encoded per RTO13
63
+
// Check that the initial value JSON is correctly populated on the mapCreateWithObjectId.initialValue property per RTO11f15, using the RTO11f4 partial ObjectOperation and correctly encoded per RTO13. Per RTO11f15, the initialValue is a JSON string of the MapCreate object itself (not wrapped in a type key).
// Check that the initial value JSON is correctly populated on the counterCreateWithObjectId.initialValue property per RTO12f10, using the RTO12f2 partial ObjectOperation and correctly encoded per RTO13
172
+
// Check that the initial value JSON is correctly populated on the counterCreateWithObjectId.initialValue property per RTO12f13, using the RTO12f2 partial ObjectOperation and correctly encoded per RTO13. Per RTO12f13, the initialValue is a JSON string of the CounterCreate object itself (not wrapped in a type key).
0 commit comments