Skip to content

Notes & Quick Ideas #5

Description

@djdarcy

Notes & Quick Ideas

Quick notes, small bugs, and ideas that don't warrant their own issue yet.

Ideas

  • Native as_resolver(): unctools could expose an object satisfying the stack's PathVariantResolver protocol (UNC <-> mapped-drive variants). dazzle-filekit currently ships a small adapter that wraps unctools' convert_to_local / convert_to_unc; a native resolver would let filekit consume unctools directly. Tracked on the Roadmap (Phase 3).
  • Consider whether find_accessible_path and a future variant-resolver should share a single code path (one probes reachability, one lists names -- related but distinct).

Quick bugs / observations

  • Upstream (git-repokit-common): sync-versions --auto corrupts CHANGELOG.md when repo-url is unset -- it rewrites real repo URLs to $GITHUB_ORG/$PROJECT_NAME placeholders, and a pre-commit hook would re-corrupt on every commit. Worked around here by setting [tool.repokit-common] repo-url; worth a fix upstream (skip URL rewriting / fail loudly when repo-url is missing, never write placeholders).
  • The .gitignore carried 5 unresolved merge-conflict regions from an old origin/dev merge (committed long ago); repaired in 0.2.1.

Notes (stack context)

  • Charter: L0 = identity/probe only, never mutate (the 0.2.0 split enforced this). Keep new capability on the right side of that line -- anything that opens/copies/moves content belongs in dazzle-filekit (L1), not here.
  • Version is autobumped from unctools/_version.py (MAJOR/MINOR/PATCH); never hand-edit the __version__ string.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestpinnedPermanently open issue

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions