# todo: dirty workaround with global nodestore to prevent node cloning. because i dont understand jsonpickle with nested objects and custom handlers yet :/
# maybe its not me but a bug https://github.com/jsonpickle/jsonpickle/issues/248 ?
# by zero changes we mean, changes where the node count did not change. e.g. if we create an index for label "myLabel" we also detect a schema change for Label "myLabel"
# this can be undesirable in some situations. to ignore such changes set `ignore_zero_changes` to True