Closed rpiazza closed 6 years ago
This bug happens because we need to pass allow_custom
to new_version
in add_markings
. I think we can assume that if we're adding markings to an object, the object has already been checked for unwanted custom properties (so we should be able to just pass allow_custom=true
where we call new_version
in add_markings
).
Other functions that call new_version
and should have the same assumption applied:
remove_markings
(for both object markings and granular markings)clear_markings
(for both object markings and granular markings)revoke
Here is the stack trace:
Traceback (most recent call last):