contract alias ls can't be used from a script

Abierto
  • ¿Algo no está bien?
#2,879 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
cli

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Rust
Estrellas
129
Forks
153
Merge medio
1 d 14 h
PR fusionados (30 d)
11

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de stellar/stellar-cli

Todos los issues de stellar/stellar-cli

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.