[
https://issues.apache.org/jira/browse/CAMEL-24715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen reassigned CAMEL-24715:
-----------------------------------
Assignee: Claus Ibsen
> camel-yaml-dsl-validator - table-driven hints instead of branches in four
> methods; drift test for the remaining hardcoded lists in the camel-jbang
> checks
> ---------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-24715
> URL: https://issues.apache.org/jira/browse/CAMEL-24715
> Project: Camel
> Issue Type: Improvement
> Components: camel-jbang, camel-yaml-dsl
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Priority: Minor
>
> The YAML validator (camel-yaml-dsl-validator, YamlValidator) post-filters the
> schema library's errors into messages that say what to write: about eighteen
> hints as branches in four methods (withStepHints, withListHint,
> withPropertyHint, withExpressionHint), each keyed on the error's keyword and
> JSON-pointer location, plus the required-expression and script checks
> (CAMEL-24698, PR 26362). The write-time checks in camel-jbang (PR 26379) were
> split into one class per check; the validator's hints were not restructured,
> to keep that PR to the behaviour.
> Tidy-up: one table of (keyword, path pattern, condition, message) with a
> small matcher, so a new hint is a row and not a branch; the existing tests
> (YamlValidator*Test) pin every message, so the change is behaviour-neutral by
> construction. Also review the remaining hardcoded lists in the camel-jbang
> checks (the endpoint options models invent, the timer's exchange properties)
> with a test that cross-checks them against the catalog, so they cannot drift.
> Noted as the tidy-up on CAMEL-24698 (comment of 2026-09-13) and in the review
> of PR 26362.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
