@edgible-team/sdk
    Preparing search index...

    Function renderTemplateConfigure

    • Re-render a catalog-deployed application at its CURRENT template version with changed parameter answers: merge the stored map with the caller's overrides (overrides win), then render exactly as a fresh deploy would — so the result carries the renderer's own templateRef + templateParameters stamp. Pure and browser-safe.

      Stored parameters the manifest does not declare are a LOUD refusal (TemplateParamsRemovedError) — at the SAME version that means the provenance is corrupt, and re-rendering would silently drop answers. An override naming an undeclared parameter is rejected by the renderer as TemplateParameterError ("is not a declared parameter").

      This helper does NOT gate the configure — call checkConfigureEligibility first — and it mints nothing: a generate: true secret parameter that becomes newly applicable (a visibility flip) is the caller's job, passed through overrides as a {secret, key?} ref.

      Parameters

      Returns {}

      TemplateParamsRemovedError stored params the manifest does not declare.

      TemplateManifestInvalidError the manifest is not .strict()-valid.

      TemplateParameterError a merged value is missing, the wrong kind, or violates constraints.

      TemplateOutputInvalidError the re-rendered document failed ApplicationSchema.