PART I
Warm-up
Reconnect with a useful idea before starting create normal and boundary cases. In one or two sentences, describe the input, output or host boundary from the previous exercise that this lesson builds on. If you are arriving directly, skim the worked example first; there is no locked prerequisite.
A rough note is enough. You can revise it after the example.
PART II
Instruction & guided example
Combine permission and data boundaries deliberately
The host distinguishes granted product-read permission from row contents. Four scenarios cross permission granted/denied with a nonempty/empty underlying dataset.
When denied, neither dataset may be inspected; both outcomes remain denied without leaking row counts. When granted, nonempty produces the matching result and empty produces ready-empty. Testing only granted-nonempty misses both permission enforcement and the empty-state UI. Do not assume case-insensitive editor highlighting changes the case-sensitive host identifiers used in the source contract.
This is a supplied exercise-host design contract. WillowScript and these cross-library integrations remain proposed and unimplemented here. The trace is a hand prediction or supplied observation for analysis, never a claimed script run. No cancellation method, WDB transaction API, permission manifest or native lifetime mechanism is invented.
Worked reasoning and supplied artifact
// Design artifact; not executable WillowScript.
// The host distinguishes granted product-read permission from row contents. Four scenarios cross permission granted/denied with a nonempty/empty underlying dataset.
// 1. Granted+nonempty -> data result.
// 2. Granted+empty -> completed empty result.
// 3. Denied+either -> no data inspection; same denial category.Illustrative example from the proposed WillowScript design. The language and WUIX/WMATH/WDB/WAUDIO/WTMP services are not implemented in the supplied source. This site has no interpreter, VM or native host and does not execute or certify the snippet.
Walk through the example, one line at a time
State 1Granted+nonempty -> data result.
State 2Granted+empty -> completed empty result.
State 3Denied+either -> no data inspection; same denial category.
Try the guided change
Reconstruct the supplied worked case first: list its inputs, intermediate decisions and final artifact. Compare each row with the explanation and identify exactly where the rejected alternative fails. Then use the changed inputs in Part IV for independent work.
- Write the supplied inputs and initial state before following the example.
- Reconstruct each intermediate calculation or host decision, then compare with the worked artifact.
- Explain why the contrasting alternative fails before attempting the changed inputs in Part IV.
PART III
Take a breather
Step back after the guided example. Look away from the screen, stretch, or reread your prediction. This is an optional learning pause, not a timer or an assessment gate.
When you return, try to name the lesson’s key idea without copying its wording. If that feels difficult, return to Part II and trace one line rather than restarting the entire lesson.
PART IV
Independent practice
Project context: Independent integration rehearsal. Build a small, understandable change around create normal and boundary cases.
Prepare the four-cell matrix with allowed observations and a row-count privacy note for denied cases.
What to produce
Prepare the four-cell matrix with allowed observations and a row-count privacy note for denied cases.
- State the intended behavior in a sentence before editing.
- Use only source-backed syntax and the host services whose contract you have been given.
- Record a normal case and a boundary or unavailable-resource case.
- Label hand predictions separately from anything actually measured in a supplied toolchain.
Syntax colors are a reading aid, not a compiler. The line you are editing stays uncolored until you move to a different line; capitalization is never changed. Drafts stay on this browser and code is not executed.
Need a hint?
Denial prevents the read itself; underlying size cannot be learned by bypassing the permission boundary. Start with the supplied state and trace each boundary separately.
A verified empty count because no rows is harmless fails because Denial prevents the read itself; underlying size cannot be learned by bypassing the permission boundary.
Original learning-path task and reference
In a media review console, demonstrate create normal and boundary cases. Integrate this section with the preceding section’s artifact; identify inputs, outputs, and host capabilities. Include .ws source and a host-resource contract; compare at least one normal case and one edge case.
import wuix.widget;
const button = widget.Button({
text: "Continue",
events: {
click: fnc() -> void {
navigator.open("dashboard");
}
}
});Where the original task needs a host API that is not supplied here, write the contract and predictions. Do not invent a runtime result.
PART V
Self-check
Use this check to notice what to revisit. It does not award a private course grade, block another page or claim to verify compiled code. Every answer has a learning explanation.
You may keep exploring even if you are unsure. Use the hint, compare the trace, and revise your explanation.
PART VI
Recap & small task
Bring the idea back to the mod feature you are building. A useful recap connects the mechanism to a decision you can make in your own code.
- Combine permission and data boundaries deliberately
- The host distinguishes granted product-read permission from row contents. Four scenarios cross permission granted/denied with a nonempty/empty underlying dataset.
- Separate source-backed behavior, host requirements and untested predictions.
One small recap task
Explain the decision in “Combine permission and data boundaries deliberately” using the supplied case, then state one input change that would invalidate your conclusion.
This marks your personal practice record only. It is not a certification or an official workspace assessment.