Ready. Start with one instruction.
Loading the learning workspace…
FROM YOUR FIRST INSTRUCTION TO A WORKING APPLICATION
Learn JavaScript from scratch through small working examples, visual experiments and complete projects. No account or AI key required.
Predict → Experiment → Build → Test → Explain
Ready. Start with one instruction.
Loading the learning workspace…
An application state can describe idle, loading, success and error explicitly. That is easier to render than a collection of conflicting booleans. This exercise models transitions as data; it does not pretend to perform a network request. A loading state should always leave loading after success or failure. Show an actionable error rather than an endless spinner.
function solve(input) {
return input.ok ? {status:"success",data:input.data} : {status:"error",message:"Try again"};
}
console.log(solve({"ok":true,"data":[1]}));{"status":"success","data":[1]}The returned value follows the operation in the helper. Compare each element or field, including the boundary case.
function solve(input) {Define a reusable function. Names inside its parentheses are parameters; actual arguments arrive when it is called. Defining the function does not run it.
return input.ok ? {status:"success",data:input.data} : {status:"error",message:"Try again"};Evaluate the expression after return, end this function call, and give that value to the caller. The result is not automatically displayed.
}Close the current instruction block.
console.log(solve({"ok":true,"data":[1]}));Evaluate the argument and display its value at this point. Quoted text is literal; an unquoted identifier reads its current binding.
function solve(input) {
return input.ok ? {status:"success",data:input.data} : {status:"error",message:"Try again"};
}
console.log(solve({"ok":false}));{"status":"error","message":"Try again"}The returned value follows the operation in the helper. Compare each element or field, including the boundary case.
function solve(input) {Define a reusable function. Names inside its parentheses are parameters; actual arguments arrive when it is called. Defining the function does not run it.
return input.ok ? {status:"success",data:input.data} : {status:"error",message:"Try again"};Evaluate the expression after return, end this function call, and give that value to the caller. The result is not automatically displayed.
}Close the current instruction block.
console.log(solve({"ok":false}));Evaluate the argument and display its value at this point. Quoted text is literal; an unquoted identifier reads its current binding.
function solve(input) {
return input.ok ? {status:"success",data:input.data} : {status:"error",message:"Try again"};
}
console.log(solve({}));{"status":"error","message":"Try again"}The returned value follows the operation in the helper. Compare each element or field, including the boundary case.
function solve(input) {Define a reusable function. Names inside its parentheses are parameters; actual arguments arrive when it is called. Defining the function does not run it.
return input.ok ? {status:"success",data:input.data} : {status:"error",message:"Try again"};Evaluate the expression after return, end this function call, and give that value to the caller. The result is not automatically displayed.
}Close the current instruction block.
console.log(solve({}));Evaluate the argument and display its value at this point. Quoted text is literal; an unquoted identifier reads its current binding.
Repair the intentionally changed operation so the example produces the exact expected result. Then try the extension without copying the answer.
function solve(input) {
return undefined; // input.ok ? {status:"success",data:input.data} : {status:"error",message:"Try again"};
}
console.log(solve({"ok":true,"data":[1]}));function solve(input) {
return input.ok ? {status:"success",data:input.data} : {status:"error",message:"Try again"};
}
console.log(solve({"ok":true,"data":[1]}));Produce mutually exclusive success or error states.
Which operation changed the result, why did it work, and what would you test next?
Use a different value that could expose a boundary or mistake. Predict the result first, run it, and explain how the concept would help in a small real application.
Related: Previous lesson Next lesson
100 lessons across 20 modules, covering variables, operators, strings, conditions, loops, functions, scope, arrays, objects, DOM, events, state, testing, asynchronous JavaScript and application development.