Skip to content

fix: opacity property's @update decorator was never renamed to @mark_changed - #40

Merged
petercorke merged 1 commit into
jhavl:mainfrom
petercorke:hotfix/update-decorator-name
Aug 9, 2026
Merged

fix: opacity property's @update decorator was never renamed to @mark_changed#40
petercorke merged 1 commit into
jhavl:mainfrom
petercorke:hotfix/update-decorator-name

Conversation

@petercorke

Copy link
Copy Markdown
Collaborator

Summary

main is currently broken -- import spatialgeometry raises
NameError: name 'update' is not defined.

#34 (opacity property) and #38 (renamed the @update decorator to
@mark_changed, since it collided with the new public SceneNode.update()
method) were both branched independently before either merged, so neither
PR's diff touched the other's code. #38 merged first; then #34's own new
opacity setter -- still using the pre-rename @update -- merged cleanly
on top with no conflict, silently reintroducing a decorator name that no
longer exists.

Test plan

  • import spatialgeometry -- confirmed NameError before this fix,
    confirmed clean after
  • Full suite: pytest tests/ -- 167 passed

…changed

main is currently broken -- `import spatialgeometry` raises
NameError: name 'update' is not defined.

jhavl#34 (opacity property) and jhavl#38 (renamed the @update decorator to
@mark_changed, since it collided with the new public SceneNode.update()
method) were both branched independently before either merged, so
neither PR's diff touched the other's code. jhavl#38 merged first, then
jhavl#34's own new opacity setter -- still using the pre-rename @update --
merged cleanly on top with no conflict, silently reintroducing a
decorator name that no longer exists.
@petercorke
petercorke merged commit 768a212 into jhavl:main Aug 9, 2026
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant