Deprecation Annotation | Skript Syntaxes

Aperta
#10 4 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@AyhamAl-Ali ci sta già lavorando.

Dal 28/12/2022.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

enhancement fixed in new site

Is this exclusive to just skript methods or would be it also be something good for skript syntax aswell?

An example case for this would be if there was ever a PR for raytrace syntax, for the most part that is just a better target block and target entity as it acts more like an exact target entity. In that case I'd view it as a means for a deprecation/removal of the target syntaxes *could also just be time for an update to raytrace

Originally posted by @Fusezion in https://github.com/SkriptLang/Skript/issues/5278#issuecomment-1365447205


Suggestion

As I stated above, I believe there should also be a new annotation in skript just like the @MarkedForRemoval but this time aimed for general skript syntax such as @Deprecation

Why

In the example above I mentioned we could theoretically remove the target block and target entity expressions if we were to ever add support for raytracing in skript. That's due to the fact raytracing is a just much exact hit compared to target attempting to get "around" it as it treats all blocks as full blocks

Adding this does another thing which is prevent removal of largely used syntax feeling like it randomly happened we'd be able to now mark stuff as Deprecated early on after introducing something to replace it and wait a few(1-2) major versions then remove it.

Lingua principale
Nessun dato sulla lingua
Stelle
5
Fork
11
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

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 SkriptLang/skript-docs

Tutte le issue di SkriptLang/skript-docs

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.