Deprecation Annotation | Skript Syntaxes #10
Labels
backend
Issues that require backend code changes (java)
enhancement
Feature request, an issue about something that could be improved, or a PR improving something.
frontend
Issues that require frontend code changes (HTML, CSS, JS)
priority: lowest
"Nice to have" updates that are not required (tiny low impact bug fixes or QoL enhancements).
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
andtarget 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 raytraceOriginally posted by @Fusezion in SkriptLang/Skript#5278 (comment)
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
andtarget 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 totarget
attempting to get "around" it as it treats all blocks as full blocksAdding 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.The text was updated successfully, but these errors were encountered: