Skip to content

Tighten changelog wording: user voice for behaviour, Internal: for refactors#79

Merged
bjmorgan merged 2 commits into
mainfrom
changelog-tighten-visibility-note
May 3, 2026
Merged

Tighten changelog wording: user voice for behaviour, Internal: for refactors#79
bjmorgan merged 2 commits into
mainfrom
changelog-tighten-visibility-note

Conversation

@bjmorgan

@bjmorgan bjmorgan commented May 3, 2026

Copy link
Copy Markdown
Owner

Summary

Two passes over the changelog to keep user-facing entries in user voice and label refactors as such for contributor scan-skipping.

User-facing changes reworded (5):

  • 0.20.0 visibility note: 'pure-string site rows' -> 'sites whose species is given as a plain label'; 'rule lookups' -> 'polyhedron rules'
  • 0.19.0 species tuple line: 'fixed at construction and can no longer be mutated' instead of 'stored as a tuple'
  • 0.19.0 atom_data write/reassignment paragraphs: compress to the user-facing rules
  • 0.19.0 read-only mapping: drop the TypeError/AttributeError protocol matrix, keep the canonical write-method names
  • 0.9.0 bond detection + deduplication: drop the MIC/27-image and four-step algorithm internals, keep the behavioural rule plus cross-ref to scenes.rst

Internal: prefix added to unlabelled refactors (2):

  • 0.10.1 BondSpec validation extraction (the user-visible colour validation fix is now its own bullet)
  • 0.7.1 _merge_expansions array-growth fix

The GitHub release notes for v0.20.0 retain their original wording; this is the in-repo source of truth for any future references.

Replace 'pure-string site rows' with 'sites whose species is given
as a plain label', and 'rule lookups' with 'polyhedron rules' to
match the user-guide language landed in #78.  Cosmetic only — the
GitHub release notes for v0.20.0 retain the original wording, but
this keeps the in-repo changelog consistent for any future
references.
Copilot AI review requested due to automatic review settings May 3, 2026 18:47

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the v0.20.0 changelog wording around AtomStyle.visible behavior so it matches the terminology used in the user guide (PR #78), keeping in-repo documentation consistent with published guidance.

Changes:

  • Clarifies that AtomStyle.visible applies to sites whose species is provided as a plain label (string), not Composition constituents.
  • Replaces “rule lookups” phrasing with “polyhedron rules” to better match existing terminology.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Six entries reworded to lead with user-visible behaviour rather
than internal API or implementation:

- 0.19.0 species tuple line: 'fixed at construction and can no
  longer be mutated' instead of 'stored as a tuple'
- 0.19.0 atom_data write/reassignment: compress two dense
  paragraphs into the user-facing rules (validation, key naming,
  reassignment-after-append, and when clear_2d_atom_data is needed)
- 0.19.0 read-only mapping: replace the TypeError/AttributeError
  protocol matrix with the user-facing summary plus the canonical
  write-method names
- 0.9.0 bond detection: drop MIC vs 27-image internals, keep the
  behavioural dispatch rule
- 0.9.0 deduplication algorithm: collapse the four-step description
  to the behavioural summary with a cross-ref to scenes.rst

Two entries that were pure refactors lacking the 'Internal:' tag
have it added:

- 0.10.1 BondSpec validation extraction (the user-visible colour
  validation fix is now its own bullet)
- 0.7.1 _merge_expansions array-growth fix
@bjmorgan bjmorgan changed the title Tighten 0.20.0 visibility note in changelog Tighten changelog wording: user voice for behaviour, Internal: for refactors May 3, 2026
@bjmorgan bjmorgan merged commit 67ab18c into main May 3, 2026
5 checks passed
@bjmorgan bjmorgan deleted the changelog-tighten-visibility-note branch May 3, 2026 19:13
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.

2 participants