Page MenuHomePhabricator

Don't consider integer CustomFields as changed when the number doesn't change
ClosedPublic

Authored by epriestley on Feb 21 2014, 4:52 PM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Dec 17, 7:00 AM
Unknown Object (File)
Mon, Dec 16, 6:46 PM
Unknown Object (File)
Dec 9 2024, 10:00 AM
Unknown Object (File)
Dec 5 2024, 2:05 AM
Unknown Object (File)
Dec 3 2024, 4:40 PM
Unknown Object (File)
Dec 2 2024, 5:32 PM
Unknown Object (File)
Dec 2 2024, 9:24 AM
Unknown Object (File)
Nov 30 2024, 1:02 AM
Subscribers

Details

Summary

Fixes T4466. We do an excessively strict effect check now, which means that these fields changing from (string) "16" to (int) 16 generates a transaction. Instead, compare integer values if the field has data in it.

Test Plan

{F116261}

(Also made updates without changing the number, which did not appear in the transaction log anymore.)

Diff Detail

Lint
Lint Skipped
Unit
Tests Skipped