-
Notifications
You must be signed in to change notification settings - Fork 36
Object.activate is deprecated. #111
Comments
+1 |
@steelbrain Said on slack is going to address this one |
I ran into this issue as well. 👍 |
👍 |
The work is happening here people #103 |
+1 |
@opponitur it's actually fixed, you might wanna upgrade your linter-jshint. |
@batjko that's super-weird.
and then see if it fixes the problem |
Well, I'd like to avoid renaming my .atom folder, lots of stuff in there I don't want to have to do again. But I will try and re-install Linter and linter-jshint, let's see if that does the trick. |
@steelbrain Did that recently because of my problems in Linter/#650 and still get the same deprecation warning. |
The file produces that error doesn't even exist :P |
When I click on the file names in the Deprecation cop it opens a file for me so at least it exists in my |
Which file does it open? |
@steelbrain The error points at the main.coffee of the Linter package, not the linter-jshint package. https://github.com/AtomLinter/Linter/blob/master/lib/main.coffee#L57 |
Also I am getting the same issue for some of the other linter-xxx sub-packages. |
What if I told you that the file it's requiring doesn't even exist, can someone post ls results of
|
@steelbrain Check my comment above. |
I actually wrote the code there that's reporting the deprecations 😅 |
|
I can't believe I did this Hahaha, I had upgraded this package to the latest API but haven't published a release yet. 🤦 |
Just pushed a release people, Enjoy. |
Well we're all humans 😆 |
AtomLinter v0.X.Y API has been deprecated. Please refer to the Linter docs to update and the latest API: https://github.com/AtomLinter/Linter/wiki/Migrating-to-the-new-API
The text was updated successfully, but these errors were encountered: