Skip to content

Filter incompatible inherited defaults when cloning a service - #74

Open
puncsky wants to merge 1 commit into
render-oss:mainfrom
puncsky:fix/filter-inapplicable-clone-defaults-20261029
Open

puncsky wants to merge 1 commit into
render-oss:mainfrom
puncsky:fix/filter-inapplicable-clone-defaults-20261029

Conversation

@puncsky

@puncsky puncsky commented Oct 30, 2026

Copy link
Copy Markdown

Summary

Filter source defaults against the clone's resolved type and runtime using the same applicability rules as validation. Explicit caller flags continue to be validated normally.

Motivation

Cloning a static site as a web service inherits publish-directory, and other cross-type/runtime clones inherit fields the destination rejects. Defaults should be limited to settings the destination accepts.

How to verify

go test ./cmd/... ./pkg/... ./internal/...
  • All 57 development packages pass on the candidate.
  • Clone tests run the actual merge/validate/request path across supported type/runtime transitions, with same-type and explicit-invalid-flag controls. This does not change API schemas or silently discard caller-supplied fields.
  • New-code lint is clean against c31e586e; full lint on unmodified main reports 92 pre-existing findings with the pinned golangci-lint v2.14.0.

Release notes

Cross-type and cross-runtime service clones drop incompatible inherited defaults.

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