inline-creation-future-phases
Inline Creation — Future Phases
Shipped
Template-Driven Note Scaffolding (Phase 2)
[templates.<name>] config sections define reusable note templates with path (supporting {{name}} and strftime), and fields (restricted to text, number, static_select). Referenced by create_template on dynamic_select fields. Validation enforces template existence, {{name}} in path, no .. traversal, unique field names, and reserved name (date, name) rejection.
Files: src/config.rs, src/autocreate.rs, tests/config.rs, tests/autocreate.rs
Sub-Form Overlay for Template Creation (Phase 2)
When allow_create + create_template is set and the user enters a novel value, a centered modal sub-form overlay appears with the template's fields. Supports text input with char-index cursor, number validation, static_select dropdowns. Submit creates the note with full frontmatter, Esc cancels. Graceful degradation to bare stub if terminal too small.
Files: src/tui/form.rs, src/app.rs
Post-Creation Command Hook (Phase 2)
post_create_command fires an Obsidian command via REST API /commands/{commandId}/ after template-driven note creation. Enables coordination with Templater and other plugins. Silently skipped on filesystem transport.
Files: src/transport/api.rs, src/transport/mod.rs, src/main.rs
Still Deferred
- Nested templates / recursive sub-forms
- Dynamic data sources in template fields (only static_select supported, not dynamic_select)
- Template inheritance or composition
- TUI configure screen support for editing
create_template/post_create_commandfields - Dataview DQL query sources for template field options