← All examples
39 / 100
Jev Breaking change detection Code Example
Catch release notes that understate a contract change.
Required user_id renamed to account_id.
Diff Required user_id renamed to account_id.
Compatibility Layer No
How should this change be classified?
0%
Breaking.
Let the application breaking.
Code
// Conceptual pseudocode — not Jev SDK syntax
const state = {
"diff": "Required user_id renamed to account_id.",
"compatibility_layer": false
};
const decision = await evaluateDecision({
state,
question: "How should this change be classified?",
options: ["Breaking","Additive","Internal only"],
});
// Your adapter normalizes the provider response.
// Tune this example threshold on labelled data.
if (decision.outcome === "Breaking"
&& decision.probability >= 0.85) {
flagBreakingChange(decision);
} else {
queueForReview(decision);
} This adapter illustrates the decision boundary. Check the official Jev docs for current API syntax.