You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From ruby 2.7 the taint checks (e.g. -T) are deprecated and will be completely removed from ruby 3.0. These taint checks were relevant when CGI was the norm but now they are barely an issue, therefore their deprecation.
Before ruby 3.0 becomes prevalent is better to remove the check or risk ALE stop working for people using ruby 3.0 or newer.
Currently ALEInfo shows the deprecation warning when working with ruby files:
<<<OUTPUT STARTS>>>
ruby: warning: ruby -T will be removed in Ruby 3.0
<<<OUTPUT ENDS>>>
The `-T` option (for "taint checking") was deprecated in ruby 2.7
and removed entirely in ruby 3.0. This causes the linter to fail
entirely for users of ruby 3.0.
This was reported in dense-analysis#3537, and then fixed in dense-analysis#3538 - but it seems as
though in 9fe7b1f, it was accidentally
and entirely undone.
This commit is essentially identical to dense-analysis#3538, aside from a path change
for the tests.
The `-T` option (for "taint checking") was deprecated in ruby 2.7
and removed entirely in ruby 3.0. This causes the linter to fail
entirely for users of ruby 3.0.
This was reported in #3537, and then fixed in #3538 - but it seems as
though in 9fe7b1f, it was accidentally
and entirely undone.
This commit is essentially identical to #3538, aside from a path change
for the tests.
From ruby 2.7 the taint checks (e.g. -T) are deprecated and will be completely removed from ruby 3.0. These taint checks were relevant when CGI was the norm but now they are barely an issue, therefore their deprecation.
Before ruby 3.0 becomes prevalent is better to remove the check or risk ALE stop working for people using ruby 3.0 or newer.
Currently ALEInfo shows the deprecation warning when working with ruby files:
Source: https://blog.saeloun.com/2020/02/18/ruby-2-7-access-and-setting-of-safe-warned-will-become-global-variable.html
The text was updated successfully, but these errors were encountered: