Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

versioned: Adjust action arguments

Chiusa
  • Qualcosa non va?
#1,310 1 commento 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@Techassi ci sta già lavorando.

Dal 23/10/2026.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
52/100
Tipo di issue
Refactoring
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
rust
Ambito
developer-experience

Direzione di ricerca

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.

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

Descrizione

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.

Lingua principale
Rust
Stelle
169
Fork
20
Merge medio
1g 2h
PR unite (30g)
25

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

Tutte le issue di stackabletech/operator-rs

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.