Recognize existing Vex package roots and canonical source entries

Aperta
  • Qualcosa non va?
#80 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
50/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
java
Ambito
tooling

Direzione di ricerca

Start with dependency issue #78 to see what foundation already exists, then locate the 'Open' entry point in the wave-for-platform codebase where a directory is loaded as a project. Read the linked Vex contract points (manifest/src/lib.rs L43/L77, src/commands/build.rs L41) to understand what a vex.ws package root and src/main.wave|lib.wave entries mean. Done looks like: multiple vex.ws roots discovered with target/ and .vex/deps excluded, a chosen manifest directory used for later commands, and manifest refresh that never fetches, builds or rewrites locks.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement help wanted priority high vex

Problem / current evidence

Current Vex loads vex.ws from the working directory and uses src/main.wave or src/lib.wave. WfP has no Vex package model; opening a monorepo must not imply that all nested examples form one supported Vex workspace.

Code and contract references

Scope / proposed contract

Discover existing local vex.ws packages, let the user select the command root, and expose canonical source entries. Use Open as the entry point; do not restore New Project.

Completion criteria

  • Represent multiple discovered packages without claiming native Vex multi-package workspace support.
  • Run later commands in the chosen manifest directory until a supported --manifest-path contract exists.
  • Mark target and managed .vex/deps content appropriately to avoid recursively treating caches as independent user projects.
  • Refresh local model changes without fetching, building, running or rewriting manifests/locks.
  • Handle malformed/missing manifests and nested roots while ordinary file editing remains available.

Dependencies and boundaries

  • Depends on #78.
  • Upstream references (not all are blockers for the bounded initial scope): Vex#25, Vex#30, Vex#89.
  • Ecosystem index: #49; existing foundations: #8.

Difficulty

Medium — requires understanding the affected tool or platform integration.

Audit baseline: Wave 509a1e46; Whale e3a12d08; Vex 71f29daa; WfP 2804fc02. This issue records source-audit findings and proposed work; no implementation or new execution is claimed. The checks above are future acceptance criteria. Prefer small fixtures and targeted validation; full builds or real debugger/IDE sessions should be explicit and necessary.

Lingua principale
Java
Stelle
0
Fork
3
Merge medio
8h 8m
PR unite (30g)
1

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di wavefnd/wave-for-platform

Tutte le issue di wavefnd/wave-for-platform

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.