contract alias ls can't be used from a script

Aperta
  • Qualcosa non va?
#2,879 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
3/5
Tempo stimato
1-2 giorni
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
cli

Direzione di ricerca

The work is in cmd/soroban-cli/src/commands/contract/alias/ls.rs: the networks are collected into a HashMap around lines 56-58 and printed with headers around lines 114-128. Read that file alongside alias show, and check how the Output system (#2635) is used by other commands. Done when one network's aliases can be requested as data, two runs give identical output, and the default listing still reads well.

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

Descrizione

What's wrong:
stellar contract alias ls lists every configured network at once, prints an "ℹ️ Aliases available for network '...'" header on stdout for each (also with -q), and has no way to pick a network or get the result as data (v28.1.0 alias/ls.rs#L114-L128). The networks also come out in a different order on every run, because they're collected in a HashMap (v28.1.0 alias/ls.rs#L56-L58); four runs with the 28.1.0 binary gave four different orders. contract alias show <name> --network <net> already returns a single ID.

Impact:
Anything that needs the list of contracts deployed on a network (a frontend build, CI, an agent, or the JS SDK's bindings plugin, which can't take aliases today, stellar/js-stellar-sdk#1755) has to parse text meant for people, and can't diff two runs.

How we found it:
HackMeridian 2026 tooling research (147 public hackathon repos): 18 of the 66 repos with CLI scripts used aliases, and several still copied contract IDs into env files by hand because their app needed them at build time. Reproduced with the 28.1.0 release binary on 1 November 2026. In #1971, maintainers suggested structured output for this command and chose to wait until someone asked for it; this is that ask.

Outcome we're after:
A script can get one network's aliases as data, the same way on every run. How to get there is up to the implementer.

Compatibility: People reading the default output keep a readable listing.

How to check:

  • Two runs in a row give identical output.
  • A script can get the aliases for one network without stripping headers or other networks' entries.
  • The default output still reads well for a person.

Related: #1971 (closed; the same command's output on stdout), #2622 (structured output), #2635 (the Output system), stellar/js-stellar-sdk#1755.

Lingua principale
Rust
Stelle
129
Fork
153
Merge medio
1g 14h
PR unite (30g)
11

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 stellar/stellar-cli

Tutte le issue di stellar/stellar-cli

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.