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
Drop successData null cleanup of source non-default rate IDs
In the staging server's actual behavior, the duplicated workspace
preserves the source's non-default rate IDs — so the optimistic clone's
keys and the eventual server keys line up and Onyx merges cleanly into
the same set of rates with no UI duplicates. The defensive null cleanup
was guarding against a hypothetical case where the server generates
fresh non-default rate IDs (which we did not observe).
Drop the cleanup to keep this PR minimal: the cloneCustomUnitWithNewIDs
fix in PolicyUtils.ts is what restores offline visibility (#89865); no
extra successData write is needed in the observed server behavior. If
the server ever switches to generated non-default IDs, that's a
follow-up patch (and would surface as a fresh duplicate-rates issue).
Also drops the now-unused getDefaultDistanceRate import from Policy.ts
and the test that asserted the absence of the cleanup write.
0 commit comments