Skip to content

Conversation

msiebeneicher
Copy link
Contributor

The purpose of this pull request

  • fixed cloning metadata
  • fixed unit test for cloning metadata

Checklist

  • make test executed successfully
  • unit test provided

- fixed unit test for cloning metadata
@msiebeneicher msiebeneicher requested a review from arnecls April 12, 2019 15:31
@msiebeneicher msiebeneicher self-assigned this Apr 12, 2019
@coveralls
Copy link

Coverage Status

Coverage increased (+0.06%) to 71.652% when pulling f6bc639 on bugfix/fix_empty_meta_data_after_cloning into 892ba2d on master.

1 similar comment
@coveralls
Copy link

Coverage Status

Coverage increased (+0.06%) to 71.652% when pulling f6bc639 on bugfix/fix_empty_meta_data_after_cloning into 892ba2d on master.

@arnecls arnecls merged commit 3b6429b into master Apr 13, 2019
@arnecls arnecls deleted the bugfix/fix_empty_meta_data_after_cloning branch April 13, 2019 20:17
arnecls added a commit that referenced this pull request Apr 13, 2019
@arnecls
Copy link
Contributor

arnecls commented Apr 13, 2019

Found and fixed an issue after merging.
The thing with CloneOriginal is that we create a copy of the current state first and then either need to clone the current metadata (to avoid changes "leaking" into the copy) or explicitly set it to nil as the original (as defined by the "freeze" operation) does not have metadata.

See commit: 7c14a24

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants