Skip to content

Fix the stripping of caseVersion from CFDocuments in v1p1 calls - #12

Merged
alail-ims merged 1 commit into
mainfrom
bug/POR-742
Aug 20, 2026
Merged

Fix the stripping of caseVersion from CFDocuments in v1p1 calls#12
alail-ims merged 1 commit into
mainfrom
bug/POR-742

Conversation

@alail-ims

Copy link
Copy Markdown
Contributor

toJSON() now sets result.caseVersion = effectiveVersion when serving as CASE 1.1, and strips the 1.1-only fields (frameworkType, subjectURI, extensions) otherwise — replacing the old logic that only ever stripped fields and never added caseVersion back. This fixes getCFDocument and getCFPackage (both call document.toJSON()) without touching GetAllCFDocuments, which was already correct via its own hand-built path.

…as CASE 1.1, and strips the 1.1-only fields (frameworkType, subjectURI, extensions) otherwise — replacing the old logic that only ever stripped fields and never added caseVersion back. This fixes getCFDocument and getCFPackage (both call document.toJSON()) without touching GetAllCFDocuments, which was already correct via its own hand-built path.
@alail-ims
alail-ims requested a review from tcouper August 20, 2026 14:58
@alail-ims alail-ims changed the title Fix the stripping of caseVersion from v1p1 calls Fix the stripping of caseVersion from CFDocuments in v1p1 calls Aug 20, 2026
@alail-ims
alail-ims merged commit 937b9c4 into main Aug 20, 2026
3 checks passed
@alail-ims
alail-ims deleted the bug/POR-742 branch August 20, 2026 15:09
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