History: Prevent polluting history

Feature Description

Currently, history is polluted for example by props that are added async in the background. Such props are for example:

  'resource.baseColor',
  'resource.isMuted',
  'resource.poster',
  'resource.posterId',

There might be more. In #9822, logic is put in place to allow excluding properties from creating separate history entries. Once we have both that and #9577 merged, we should have everything in place to not pollute history anymore.

Alternatives Considered

Additional Context

[miina]

Adding these values to be ignored means that the values will be ignored only if only that value changes, if the change is included in a larger change, the value will still be saved. E.g. if only isMuted changes, it won’t cause a separate history entry, however, if isMuted is included within other changes, it will still be saved.

Some testing showed that adding the following to the ignore list don’t seem to cause issues:

  'resource.baseColor',
  'resource.id',
  'resource.isMuted',
  'resource.posterId',
  'resource.poster,'

If I understand correctly then resource.poster does not change when manually changing the poster – element.poster will be change in that case, element.resource.poster is always the original poster. Thus it should be ok to ignore this value changing causing a new history entry. LMK if that’s incorrect.

I’ll do some more testing tomorrow. With these ignored values, two clicks of “Undo” are needed to undo uploading a new video to the Page (as opposed to 5 on main), will try to track down what’s still causing the extra step.

[spacedmonkey]

I would also add 'resource.blurHash' 'resource.id'