Reassess usage of blockUpdateMarkers in the code about fluidframework HOT 3 CLOSED

@anthony-murphy, it would be great to make a decision here, given that in the past that caused data corruptions.
Is there good reason to support blockUpdateMarkers and not just remove this option from API surface?
Whatever it is, we should agree on a plan.
Marking as good first issue, as once we have a decision, it's rather easy to implement.

from fluidframework.

@anthony-murphy, ping. Can we assign it to Paul in August? :)

from fluidframework.

@anthony-murphy, I want to assign this task to Kian, assuming the resolution here - we will remove blockUpdateMarkers from code (and assume value of true in merge tree implementation).
One thing to point out - code only tests static MergeTree.blockUpdateMarkers, which is true, while this.options is not used at all in merge tree! I'd suggest removing options concept altogether (though it makes it harder to add options in the future if we want to).

Feedback?

from fluidframework.