Skip to content

docs(config): document pattern-prefixed knob naming (#379)#394

Closed
trilamsr wants to merge 1 commit into
mainfrom
docs/config-knob-naming-379
Closed

docs(config): document pattern-prefixed knob naming (#379)#394
trilamsr wants to merge 1 commit into
mainfrom
docs/config-knob-naming-379

Conversation

@trilamsr

@trilamsr trilamsr commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Summary

config.go carries three knob-naming styles (bare NCCLHangThreshold, prefixed CheckpointerHangBackwardWindow, top-level JoinWindow). The prefixed shape is correct going forward; renaming the bare names for v1.0-rc1 would break every existing values.yaml.

Root cause

Convention emerged across waves, never written down. Future detectors had no signal to pick the prefixed shape.

Fix

Add an 8-line top-of-file comment documenting the convention. No code/field renames. v2.0 nesting deferred (see issue body).

Test plan

  • golangci-lint, vet, attribute-namespace-check (pre-push hook) — green
  • go build ./module/processor/patterndetectorprocessor/... — green

Closes #379.

docs: document pattern-prefixed knob naming convention in `config.go` — new per-pattern knobs use `<Pattern><Knob>`; bare names retained for backward-compat.

New per-pattern knobs MUST use <Pattern><Knob> prefix. Bare names (NCCLHangThreshold etc.) kept for backward-compat with pre-v0.4 values.yaml; no rename in v1.0-rc1. v2.0 may nest. Closes #379.

Signed-off-by: Tri Lam <tri@maydow.com>
@trilamsr

trilamsr commented Jun 1, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #392 which bundles #381+#383+#379.

@trilamsr trilamsr closed this Jun 1, 2026
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.

chore(config): document pattern-prefixed knob naming convention (v1.0-rc1 cosmetic / v2.0 nest)

1 participant