DanielLeens commented on issue #11616: URL: https://github.com/apache/seatunnel/issues/11616#issuecomment-5541751559
Thanks @CryoThrust. The proposed result contract matches the design boundary already selected for the first implementation slice. PR #12065 is now the active path for the reusable config-level validation result model, so please put field-name, category-vocabulary, null-handling, and compatibility feedback on that PR rather than opening a parallel implementation. The contract should stay transport-independent: schemaVersion, valid, and config-level phase are stable semantics; errors and warnings remain arrays; diagnostics use stable categories and optional location, plugin, and optionPath; messages stay sanitized and human-readable; and the existing --check output and exit behavior remain unchanged. A versioned fixture plus deterministic serialization tests are the right acceptance gate before a CLI, MCP, or REST adapter is proposed. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
