Skip to content

Allow framework authors to manually control framework versions - #13

Open
alail-ims wants to merge 1 commit into
mainfrom
task/POR-741
Open

Allow framework authors to manually control framework versions#13
alail-ims wants to merge 1 commit into
mainfrom
task/POR-741

Conversation

@alail-ims

Copy link
Copy Markdown
Contributor
  • toCasePackage.ts — removed incrementVersion()/DEFAULT_VERSION, version is now a straight passthrough of meta.version (undefined stays undefined), and the incrementVersion option was stripped from frameworkToCfDocument, frameworkToCfPackage, and FrameworkExportParams.
  • EditorCanvas.tsx — dropped incrementVersion: true/false from both call sites and updated the stale comment.
  • NodePropertiesPanel.tsx — version is now a free-text input (same pattern as title/creator/publisher) instead of a read-only, conditionally-hidden display.
  • Added toCasePackage.test.ts covering passthrough, no-default-when-unset, and no-auto-increment-across-saves.

…ion is now a straight passthrough of meta.version (undefined stays undefined), and the incrementVersion option was stripped from frameworkToCfDocument, frameworkToCfPackage, and FrameworkExportParams.

- EditorCanvas.tsx — dropped incrementVersion: true/false from both call sites and updated the stale comment.
- NodePropertiesPanel.tsx — version is now a free-text input (same pattern as title/creator/publisher) instead of a read-only, conditionally-hidden display.
- Added toCasePackage.test.ts covering passthrough, no-default-when-unset, and no-auto-increment-across-saves.
@alail-ims
alail-ims requested a review from tcouper August 20, 2026 16:24
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