I don’t want to have to re-upload edited versions of the plugins I use because they have this warning, or go through my old projects just so this isn’t spamming in the output of the F9 console.
7 Likes
I disagree, but I do think the warning should display the script/line that triggered it.
3 Likes
Mind posting a reason why you disagree? Curious why you want to keep the warning up.
Well the whole reason that warning is there: so that you know that you’re setting FormFactor somewhere. If you didn’t know that, then when/if they remove the property (they can because it’s deprecated), then your script suddenly crashes on those lines and you’d be pissed at the staff for not warning you enough beforehand.
In other words, don’t ignore the warnings, you should adjust your scripts.
And for plugins I don’t own and aren’t regularly updated?
Then it’s not your responsibility anyway? It’s the responsibility of the guy who owns the plugin. I don’t really see how that situation is an argument to hide the important warning for all developers.
What’s most annoying about it is that in my instance serializer the list of properties is order-specific so I can’t just remove FormFactor because then every old string will be trying to set the wrong properties to the wrong values because they would all be one off. I had to go around this by adding a line to specifically not set the property if it’s called FormFactor, otherwise I get ten thousand lines of output warning spam.
My experience animating.
please
4 Likes
You guys do realise that if you get 1000 warnings, that’s 1000 moments that can potentially cause an error in the future if they remove the property entirely? You’ll really want to look into that and edit your code. Hiding the warning will decrease your ability to see these possible points of failure.
I had to whip up a command bar script to find all occurrences in Mad Games…
That’s the default Roblox animation editor causing those warnings, lol.
Animation editor warning have been fixed (along with more bugs) I just haven’t published that update yet. Preparing to activate a certain feature before I do that.
5 Likes
Crazy idea incoming guys. What if… maybe, just maybe… we had the option to suppress certain warnings. Just because your favorite plugin developer didn’t update their plugin yet doesn’t mean your productivity has to tank because your output is cluttered. Or you know, line + location always helps.
Also, @buildtomas: When was the last time they removed a property labelled deprecated? Lowercase className has been deprecated for a very long time now. It doesn’t throw warnings. Lowercase BasePart.size does throw a warning, though. Hardly anyone even knows about that one. It hasn’t gone away. Lowercase BodyPosition.position is deprecated and we have no warnings for that. tl;dr: roblox has a history for having inconsistent API and error handling, this is no different.
Edit: Another crazy idea: maybe show the warning just once per script?
1 Like
Missed a h there >:0
Regarding the rest of the paragraph, you argue that there is no need to switch to newer APIs or remove API calls, but the whole definition of deprecation is that they won’t remove them immediately to give you time to switch over to the newer API calls. Ignoring the warnings completely goes against that. See definition of deprecation in software on Wikipedia. Just because they haven’t removed deprecated API yet doesn’t mean that they won’t in the future, there’s no way to tell.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.