Skip to content

Specify path-stored fields for 0.3.0-rc.6 - #66

Merged
callumalpass merged 1 commit into
mainfrom
feat/path-stored-fields
Nov 4, 2026
Merged

callumalpass merged 1 commit into
mainfrom
feat/path-stored-fields

Conversation

@callumalpass

Copy link
Copy Markdown
Collaborator

Summary

  • Adds collection.path.fields and {field:FORMAT} date placeholders, so a field's value can live in the record's path (TaskNotes titles as filenames, daily-note dates). See notes/SN-102.md.
  • Rewrites Chapters 07 and 12, with pointer edits in the other chapters, the type-file schema, and an rc.6 CHANGELOG entry.
  • Adds 53 fixtures in tests/v0.3/core/path-fields.yaml and a round-trip check in scripts/concurrent_edits_model.py.

Supersedes the filename-derived values of SN-056. rc.6 stays a draft and is not tagged here.

Testing

  • python scripts/check_v03_tests.py: 212 executable tests, 243 adapter-target tests, ok
  • python scripts/check_test_levels.py: passed
  • All 53 fixtures pass against the runtime engine in the companion mdbase-connect change.

A type can now declare that a field's value lives in the record's path,
through collection.path.fields and {field:FORMAT} date placeholders, so a
task title kept as the filename or a daily note's date is declared once
and every tool reads and writes it the same way.

Decoded values are persisted values but take no part in type matching, and
are never written to frontmatter. A write that changes a stored field moves
the record atomically. Adds 53 fixtures in core/path-fields.yaml, the
type-file schema change, the concurrent edits model round-trip check, and
SN-102.
@callumalpass
callumalpass merged commit 329c8b4 into main Nov 4, 2026
20 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