Skip to content
This repository has been archived by the owner on Oct 24, 2024. It is now read-only.

Fix name permanence behaviour in update method #178

Merged

Conversation

TomNicholas
Copy link
Member

@TomNicholas TomNicholas commented Jan 4, 2023

  • An overlooked part of Name permanence #116
  • Tests added
  • Passes pre-commit run --all-files
  • New functions/methods are listed in api.rst
  • Changes are summarized in docs/source/whats-new.rst

@TomNicholas TomNicholas added the bug Something isn't working label Jan 4, 2023
@TomNicholas TomNicholas enabled auto-merge (squash) January 4, 2023 16:10
@TomNicholas TomNicholas merged commit 4eb70a6 into xarray-contrib:main Jan 4, 2023
flamingbear pushed a commit to flamingbear/rewritten-datatree that referenced this pull request Jan 19, 2024
…e#178

* test for name permanence in update

* ensure node is copied on update

* [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

* black

* whatsnew

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant