Model ordered lists, nested settings, and typed event configuration — Connect the previous skills

PART I

Warm-up

Reconnect with a useful idea before starting model ordered lists, nested settings, and typed event configuration. 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

Connect list order to a view without inventing a sort

An ordered collection carries order and identity as different facts. A displayed position may change when elements move; a stable record identity should continue naming the same record. Predict transformations using supplied tiny inputs before choosing a configuration or host API.

Host rows are [{id:8, priority:2},{id:3, priority:1},{id:6, priority:2}]. Required view sorts ascending priority, then ascending id to break ties. Sorting behavior is a specified exercise transformation, not an assumed collection builtin.

Worked reasoning: Priority1 id3 comes first. Priority2 rows tie, so id6 precedes8. Output ids3,6,8 is deterministic even when source rows arrive in a different order.

Failed alternative: Sorting only priority leaves the tie order unspecified under this contract, so a different host arrival order can visibly reshuffle equal-priority rows.

Worked reasoning and supplied artifact

Input:[8:p2,3:p1,6:p2]
Comparator keys:(priority,id) ascending
Sorted:[3:p1,6:p2,8:p2]
Alternate arrival:[6:p2,8:p2,3:p1] ->same required output

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.

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: Reusable configuration workspace. Build a small, understandable change around model ordered lists, nested settings, and typed event configuration.

Order ids9: p3,4: p1,2: p3 by priority then id. Explain the effect of omitting the tie-breaker.

What to produce

A key-comparison table and two-arrival-order output comparison.

• 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.

import wuix.widget;
const button = widget.Button({
    text: "Continue",
    events: {
        click: fnc() -> void {
            navigator.open("dashboard");
        }
    }
});

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.

• Connect list order to a view without inventing a sort
• Order ids9: p3,4: p1,2: p3 by priority then id. Explain the effect of omitting the tie-breaker.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Write every ordering key in priority order, including tie resolution.

This marks your personal practice record only. It is not a certification or an official workspace assessment.