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
As far as I can understand, the SASS-code in the minima theme has in fact been corrected so it does not cause the deprecation warnings. Long ago, no later than February 2023 (source). But for some reason the latest 4.3.3 release of Jekyll (December 2023), still causes these warnings.
I have found several work-arounds in the above threads, and of course I can overcome this. But its really a shame that when somebody (e.g. me, two weeks ago) tries out Jekyll for the first time, and follows the very short and simple quick start tutorial, they are met with these warnings.
I wonder why it has not been fixed in the latest 4.3.3 (Dec 27 2023). Is there some compatibility issue that I don't understand? Or is it a simple lack of manpower? Are deprecation warnings considered not to be a priority and something that can easily wait months or years? Or was it simply forgotten to fix this issue in the latest release?
I'm not here to complain, I'm here partly because I am curious (I simply don't understand why it has not been fixed), and partly because I want to let you know, that this gives newcomers a poor first impression. And let me add that I am very new to Ruby, and not a professional developer, so I hope you won't be too hard on me :)
All the best :) And thanks for all the work you have put into this!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have read several threads regarding this, including many replies by @ashmaroli and @mattr-.
As far as I can understand, the SASS-code in the minima theme has in fact been corrected so it does not cause the deprecation warnings. Long ago, no later than February 2023 (source). But for some reason the latest 4.3.3 release of Jekyll (December 2023), still causes these warnings.
I have found several work-arounds in the above threads, and of course I can overcome this. But its really a shame that when somebody (e.g. me, two weeks ago) tries out Jekyll for the first time, and follows the very short and simple quick start tutorial, they are met with these warnings.
I wonder why it has not been fixed in the latest 4.3.3 (Dec 27 2023). Is there some compatibility issue that I don't understand? Or is it a simple lack of manpower? Are deprecation warnings considered not to be a priority and something that can easily wait months or years? Or was it simply forgotten to fix this issue in the latest release?
I'm not here to complain, I'm here partly because I am curious (I simply don't understand why it has not been fixed), and partly because I want to let you know, that this gives newcomers a poor first impression. And let me add that I am very new to Ruby, and not a professional developer, so I hope you won't be too hard on me :)
All the best :) And thanks for all the work you have put into this!
Beta Was this translation helpful? Give feedback.
All reactions