Workspace search beyond entry-module's directory #14
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
load_workspaceonly finds sibling.ail.jsonfiles in the same directory as the entry module, so any consumer of prelude/std in a subdirectory has no way to resolve cross-module imports. Add either a--workspace-rootflag onail check/ail build/ail run, or upward-search from the entry module's directory. Alternatively ratify the flat-workspace assumption in DESIGN.md if intentional.context: fieldtest 2026-05-11 — fieldtest fixtures could not be placed under
examples/fieldtest/because of this; predates the canonical-type-names milestone but surfaces every time.Closing as subsumed by #34, which tracks the same root cause (the workspace loader resolves imports only against the entry module's directory) with a concrete repro, the fieldtest symlink workaround, and the companion unfound-module diagnostic fix. The flat-workspace "ratify in design if intentional" alternative is preserved there. Verified still-open behaviour 2026-06-02:
load_modules_withresolvesroot_dir.join("<name>.ail")against the entry's parent directory only; no--workspace-rootflag exists.