Import only the public APIs you use — Review and demonstrate

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

Review imports as a minimal public surface proposal

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 sample import review packet lists a pure price helper with no service dependency, a screen adapter with documented WUIX needs and a data adapter with proposed WDB plus products/field contracts. Each entry records used APIs, unresolved export linkage and required capabilities. This explains dependency choices rather than rewarding the smallest number of lines blindly.

Minimal does not mean deleting a genuinely required dependency or guessing implicit globals. It means every requested API has a clear purpose and every host resource has a separate contract. Runtime availability remains unverified in this public design exercise.

Worked reasoning and supplied artifact

// Worked contract artifact:
// The sample import review packet lists a pure price helper with no service dependency, a screen adapter with documented WUIX needs and a data adapter with proposed WDB plus products/field contracts. Each entry records used APIs, unresolved export linkage and required capabilities. This explains dependency choices rather than rewarding the smallest number of lines blindly.

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

Audit the sample packet and justify each dependency from a concrete operation.

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

Submit an import/resource review for a mod feature with one pure rule and one native integration. Include unused-dependency removal, one required service and one explicit denied resource case.

What to produce

A purpose-based import/use/capability inventory with source-status and evidence limits.

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

• Review imports as a minimal public surface proposal
• Audit the sample packet and justify each dependency from a concrete operation.
• Separate source-backed behavior, host requirements and untested predictions.

One small recap task

Audit the sample packet and justify each dependency from a concrete operation.

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