Import only the public APIs you use — Discover and trace

PART I

Warm-up

Reconnect with a useful idea before starting import only the public apis you use. 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

Read a narrow dependency path before using a service

An import requests a named public API from the proposed library hierarchy. A narrow import is not evidence that sibling modules are visible, that native services are installed or that a capability is granted. Existing Willow module experience helps you ask precise questions, but it cannot fill missing WillowScript host contracts.

The worked UI design imports wuix.widget.button and wuix.layout. Sample dependency table: button path = button-related API request; layout path = layout-related request; used operation = source-named wuix.mount; unresolved = how the host exposes that operation through the supplied modules. The source example is illustrative, so record the dependency question instead of declaring a verified resolver result.

Do not infer sibling APIs such as audio from a WUIX path. Library → Module → Submodule → API → Parameters describes the proposed hierarchy, not a blanket permission grant or proof every combination is implemented.

Worked reasoning and supplied artifact

import wuix.widget.button;
import wuix.layout;
// Review each imported public surface against the supplied host contract.

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

Write the two import paths and the specific service uses, then mark any linkage that requires the host’s documented export map.

• 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: Shared pricing rules. Build a small, understandable change around import only the public apis you use.

Review a small native screen draft for the minimum documented WUIX dependencies. List what each import is intended to support and one API you must not assume is available.

What to produce

An import/use table, a pending export-map question and an explicit no-sibling-assumption note.

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

fnc add(a: i32, b: i32) -> i32 {
    return a + b;
}
fnc main() -> i32 {
    return add(2, 3);
}

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.

• Read a narrow dependency path before using a service
• Write the two import paths and the specific service uses, then mark any linkage that requires the host’s documented export map.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Write the two import paths and the specific service uses, then mark any linkage that requires the host’s documented export map.

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