Mike Gerwitz c5194b4ec5 StagingBucket: Do not process non-changes ... Since changes trigger any event observers---which can be expensive---it is ideal to ignore sets that do not result in any changes to the bucket. This also resolves issues with systems that are confused by empty diffs. * src/bucket/StagingBucket.js (_hasChanged): Add method. (setValues): Use it. * test/bucket/StagingBucketTest.js: Add test case. DEV-2299		2017-02-20 12:16:24 -05:00
..
bucket	StagingBucket: Do not process non-changes	2017-02-20 12:16:24 -05:00
dapi	Remove debugging console.log from XhrHttpImplTest	2016-04-19 00:05:47 -04:00
event	FieldVisibilityEventHandler: use new DataValidator API	2017-02-09 15:20:23 -05:00
store	Add DiffStore	2017-01-30 00:29:25 -05:00
system	system.client: working data.diffStore	2017-01-30 00:43:13 -05:00
ui	Correct and test GeneralStepUi#scrollTo	2016-08-05 11:45:09 -04:00
validate	DataValidator: Hold concurrent requests	2017-02-17 11:31:32 -05:00
pre.js	add es6-promise shim	2016-03-01 00:48:37 -05:00