10. Decisions using conditions
Module 2 · 20 minutes · Lesson 9; earlier service and JavaScript fundamentals
Open Interactive LessonDiscover
How can you use decisions using conditions without changing the wrong data?
- Explain decisions using conditions in your own words
- Trace the actual console result from the source
- Repair the supplied failing operation and verify the result
Predict
Which values or resources will change, and which should stay unchanged? Write your prediction before execution.
Understand
An if statement chooses whether to execute a block. Conditions should express the actual boundary, including whether equality counts. Strict equality avoids implicit type conversion. Else covers the alternative path, but a business rule can require additional validation before either path. Test below, exactly at and above a threshold rather than only one happy example.
Example 1: Working automation
Equality belongs to the review branch in this rule. The sample deliberately sits at the boundary.
function main() {
const amount = 100;
if (amount >= 100) {
console.log("Review required");
} else {
console.log("Standard");
}
}Important line explanations
- Line 1: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 2: const amount = 100;
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: if (amount >= 100) {
- Evaluate a condition and execute this branch only when it is true. Test the opposite path too.
- Line 4: console.log("Review required");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 5: } else {
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 6: console.log("Standard");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 7: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 8: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"Review required"
],
"error": null,
"resource": "logs",
"value": null
}Example 2: Investigate a reproducible failure
Predict the effect of amount > 100 and identify the first mismatch. This example is intentionally faulty.
function main() {
const amount = 100;
if (amount > 100) {
console.log("Review required");
} else {
console.log("Standard");
}
}Important line explanations
- Line 1: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 2: const amount = 100;
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: if (amount > 100) {
- Evaluate a condition and execute this branch only when it is true. Test the opposite path too.
- Line 4: console.log("Review required");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 5: } else {
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 6: console.log("Standard");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 7: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 8: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"Standard"
],
"error": null,
"resource": "logs",
"value": null
}Example 3: Separate setup from execution and inspect repeat behavior
Call the same named operation twice. Compare outputs and resource counts to learn whether this operation is idempotent. Repeated creation is deliberately visible; real exports require a rerun policy.
function lessonAction() {
const amount = 100;
if (amount >= 100) {
console.log("Review required");
} else {
console.log("Standard");
}
}
function main() {
lessonAction();
lessonAction();
}Important line explanations
- Line 1: function lessonAction() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 2: const amount = 100;
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: if (amount >= 100) {
- Evaluate a condition and execute this branch only when it is true. Test the opposite path too.
- Line 4: console.log("Review required");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 5: } else {
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 6: console.log("Standard");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 7: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 8: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 9: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 10: lessonAction();
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 11: lessonAction();
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 12: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"Review required",
"Review required"
],
"error": null,
"resource": "logs",
"value": null
}Example 4: Add a diagnostic boundary around the operation
Observe start, successful completion or a rethrown failure. This optional professional pattern adds error context without swallowing the error or rolling back changes.
function lessonAction() {
const amount = 100;
if (amount >= 100) {
console.log("Review required");
} else {
console.log("Standard");
}
}
function main() {
console.log("Start: Decisions using conditions");
try { lessonAction(); console.log("Completed operation"); }
catch(error) { console.error("Failed operation: " + error.message); throw error; }
}Important line explanations
- Line 1: function lessonAction() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 2: const amount = 100;
- Initialize a local binding. const prevents reassignment of that binding, but does not freeze a referenced object.
- Line 3: if (amount >= 100) {
- Evaluate a condition and execute this branch only when it is true. Test the opposite path too.
- Line 4: console.log("Review required");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 5: } else {
- Follow this operation using the surrounding named values. Compare the actual recorded state with the lesson’s specific explanation below.
- Line 6: console.log("Standard");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 7: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 8: }
- Close the current block. Indentation makes scope and the function boundary visible.
- Line 9: function main() {
- Define a named block of instructions. Run Script calls main; helpers run only when called.
- Line 10: console.log("Start: Decisions using conditions");
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 11: try { lessonAction(); console.log("Completed operation"); }
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 12: catch(error) { console.error("Failed operation: " + error.message); throw error; }
- Record diagnostic evidence. A log does not grant permissions or prove a later side effect succeeded.
- Line 13: }
- Close the current block. Indentation makes scope and the function boundary visible.
Exact expected output and resource
{
"logs": [
"Start: Decisions using conditions",
"Review required",
"Completed operation"
],
"error": null,
"resource": "logs",
"value": null
}Build and test
Repair the supplied script so that: Equality belongs to the review branch in this rule. The sample deliberately sits at the boundary. Preserve other source data. Checks compare observable output and the named resource, not exact source text.
function main() {
const amount = 100;
if (amount > 100) {
console.log("Review required");
} else {
console.log("Standard");
}
}Graduated hints
Hint 1
Inspect the operation containing amount > 100. Compare it with the stated rule and the first mismatch.
Hint 2
The repair concerns amount >= 100. Change only the relevant argument, operator or method; rerun with fresh input.
Hint 3
The reference uses amount >= 100 where the broken source uses amount > 100. Explain why before applying it.
Reference solution
function main() {
const amount = 100;
if (amount >= 100) {
console.log("Review required");
} else {
console.log("Standard");
}
}Explain and reflect
Which operation proves the intended result in decisions using conditions? Which wrong input would expose a weakness, and what would remain unchanged?
Adapt the calculation or validation to a second realistic case. Write its expected result before running. Demonstrate one invalid case and explain whether the side effects should be rolled back or retried.
Troubleshooting
If the console is empty, inspect the logs preview: this script may work through state changes. If the function is missing, select main. For a service error inspect the first failed timeline entry and its arguments. Use Manual unless investigating a trigger. Changing input data also changes the expected result; restore sample data before the authored checks.
Knowledge check
Explain the key method or operator. Give an exact output for a second input, plus one invalid case. Verify the result in the interactive lesson; written explanations need self or educator review.
Optional AI practice
Explain this concept using the source above. Help implement one small extension and define its tests. Review/debug the source using its actual expected output; cite real method references and never claim execution.