Casilian StudiosCASILIANMODDING SCHOOL

WillowScript (.ws) is a proposed, not-yet-implemented language. Examples and library integrations here are illustrative design exercises, not verified runnable programs.

WillowScript Professional · Repair an unstable row-index selection

Filter and order a result — Flash-check repair

Filter and order a result: flash-check repair.

Practice saves only on this browser.

PART I

Warm-up

Reconnect with a useful idea before starting filter and order a result. 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

Repair an unstable row-index selection

A user selects row index0 when A stock=2 and B stock=5. A refresh changes B stock to1 and sorting moves B first.

Index0 now refers to B, so retaining the index changes the selected record unintentionally. Preserve A’s stable authorized id and resolve its new position. If A disappears, show selection-unavailable rather than silently selecting another row.

Write the intermediate states explicitly before proposing a code change. The example below remains an illustrative source anchor; this new case changes the inputs or the host requirement. WillowScript and these library services are proposed and unimplemented here. Treat new policies as supplied exercise contracts, and keep hand predictions distinct from native execution evidence.

Worked reasoning and supplied artifact

// PAPER FIXTURE — Repair an unstable row-index selection
// Manual worked artifact; comments below are not executable source.
// INPUT / CONTRACT: A user selects row index0 when A stock=2 and B stock=5. A refresh changes B stock to1
// and sorting moves B first.
// DERIVATION / EXPECTED ARTIFACT: Index0 now refers to B, so retaining the index changes the selected
// record unintentionally. Preserve A’s stable authorized id and resolve its new position. If A disappears,
// show selection-unavailable rather than silently selecting another row.

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
  1. // PAPER FIXTURE — Repair an unstable row-index selection

    This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.

  2. // Manual worked artifact; comments below are not executable source.

    This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.

  3. // INPUT / CONTRACT: A user selects row index0 when A stock=2 and B stock=5. A refresh changes B stock to1

    This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.

  4. // and sorting moves B first.

    This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.

  5. // DERIVATION / EXPECTED ARTIFACT: Index0 now refers to B, so retaining the index changes the selected

    This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.

  6. // record unintentionally. Preserve A’s stable authorized id and resolve its new position. If A disappears,

    This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.

  7. // show selection-unavailable rather than silently selecting another row.

    This comment explains intent for a reader. It is not an operation and should not be counted as an executed result.

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.

Your drafts remain here. Continue whenever you are ready.

PART IV

Independent practice

Project context: Inventory review workspace. Build a small, understandable change around filter and order a result.

Draw old/new ordered tables and selected-id state for update and deletion cases.

What to produce

Draw old/new ordered tables and selected-id state for update and deletion 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?

Index0 now refers to B, so retaining the index changes the selected record unintentionally. Preserve A’s stable authorized id and resolve its new position. If A disappears, show selection-unavailable rather than silently selecting another row.

The tempting answer “The old row index” does not satisfy this case. Index0 now refers to B, so retaining the index changes the selected record unintentionally. Preserve A’s stable authorized id and resolve its new position. If A disappears, show selection-unavailable rather than silently selecting another row.

Original learning-path task and reference

In a rhythm-game audio editor, demonstrate filter and order a result. Explain the flash answer, locate a plausible mistake, and repair the relevant part of your task. Include .ws source and a host-resource contract; compare at least one normal case and one edge case.

import wdb;
domain Inventory {
    const lowStock = wdb.query({
        from: products,
        select: [id, name, stock],
        where: [[ stock < 10 ]],
        order: { by: stock, direction: ascending }
    });
}

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.

What should preserve selection identity?

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.

  • Repair an unstable row-index selection
  • A user selects row index0 when A stock=2 and B stock=5. A refresh changes B stock to1 and sorting moves B first.
  • Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Change one input in this case and state which intermediate state or calculation must be recomputed. Explain why “The old row index” is not justified.

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

Your practice, on this browser

No public account is created. Drafts and lesson progress stay in this browser’s local storage. They do not automatically follow you to another device and can be lost if browser storage is cleared.

Export a private progress file to keep a copy, then import it on another browser when you want to move your work. Treat that file as your own writing; it can contain your practice drafts.