Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

versioned: Adjust action arguments

Cerrado
  • ¿Algo no está bien?
#1,310 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@Techassi ya está trabajando en esto.

Desde el 23/10/2026.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
52/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
rust
Área
developer-experience

Línea de trabajo

Start by reading the crate that parses and applies the versioned attribute arguments, then check its tests and examples for since and from_ usage. The issue proposes renaming these to in and prev_ or previous_, but leaves the preferred prefix open. Done means the argument names are updated consistently and the proposed prev_docs use for deprecated actions is supported.

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

Descripción

Current state

Currently, all actions use the since argument to specify since which version a particular change was introduced. Additionally, all arguments describing previous facts, like the item name, the item type, and the item docs use the from_ prefix.

struct Foo {
    #[versioned(changed(
        since = "...",
        from_name = "...",
        from_type = "...",
        from_docs = "..."
    ))]
    bar: bool,
}

Initially, this made sense to use both these terms, because e.g. a field's name changed from foo to bar. As such, the argument name from_name makes sense. We recently noticed that both terms are not ideal, especially the combination #[versioned(changed(since = "...", from_docs = "..."))].

Suggestion

I suggest renaming these arguments in the following fashion:

  • since -> in. This maps well for all actions and in which version a particular change happened:
    • "added in ..."
    • "changed in ..."
    • "deprecated in ..."
  • from_ -> prev_ or previous_. This better expresses what the fact's value was previously:
    • "the previous name was ..."
    • "the previous type was ..."
    • "the previous docs were ..."
struct Foo {
    #[versioned(changed(
        in = "...",
        prev_name = "...",
        prev_type = "...",
        prev_docs = "..."
    ))]
    bar: bool,
}

This change also enables us to add support for from_docs/prev_docs to deprecated action for example. prev_docs just makes way more sense in this context.

Lenguaje dominante
Rust
Estrellas
169
Forks
20
Merge medio
1 d 6 h
PR fusionados (30 d)
22

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 stackabletech/operator-rs

Todos los issues de stackabletech/operator-rs

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.