Repository navigation
Release v4.116.0
Render plans can now describe implementation gaps: places where a model describes behaviour in prose and the rendered code needs a hand-written body. This release adds the contracts only. Nothing produces gaps yet, and existing plans and their digests are unchanged.
Added
ArtifactImplementationGap,ArtifactImplementationStub,ArtifactImplementationContextandArtifactImplementationBodyLocatordescribe a gap, its requirement id, role, hints, and each typed stub with its file, signature, body location and acceptance specifications. (part of #316)ArtifactRenderPlan.ImplementationGaps, forwarded throughCratisPlanResult. A plan with gaps includes them in its digest; a plan without gaps keeps its existing digest. (part of #316)ImplementationGapMode(RefuseorStub) onCratisPlanOptionsandCratisRenderingOptions. It defaults toRefuseand has no effect until a target supports stubs. (part of #316)