Skip to content
This repository has been archived by the owner on Aug 7, 2023. It is now read-only.

Object.activate is deprecated. #111

Closed
Eschon opened this issue Jul 8, 2015 · 23 comments
Closed

Object.activate is deprecated. #111

Eschon opened this issue Jul 8, 2015 · 23 comments

Comments

@Eschon
Copy link

Eschon commented Jul 8, 2015

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

Object.activate (/Users/egon/.atom/packages/linter/lib/main.coffee:57:8)
Package.activateNow (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:240:19)
<unknown> (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:221:30)
Package.measure (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:165:15)
Package.activate (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:213:14)
PackageManager.activatePackage (/Applications/Atom.app/Contents/Resources/app.asar/src/package-manager.js:452:21)
@jonnitto
Copy link

jonnitto commented Jul 8, 2015

+1

@iam4x
Copy link
Member

iam4x commented Jul 8, 2015

@steelbrain Said on slack is going to address this one

@stramel
Copy link

stramel commented Jul 8, 2015

I ran into this issue as well. 👍

@nandak522
Copy link

👍

@steelbrain
Copy link
Contributor

The work is happening here people #103

@opponitur
Copy link

+1

@steelbrain
Copy link
Contributor

@opponitur it's actually fixed, you might wanna upgrade your linter-jshint.

@batjko
Copy link

batjko commented Jul 10, 2015

Still getting this though:
image

image

@steelbrain
Copy link
Contributor

@batjko that's super-weird.
You might wanna try

mv ~/.atom ~/.atom-bkp
apm install linter
apm install linter-jshint

and then see if it fixes the problem

@batjko
Copy link

batjko commented Jul 10, 2015

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.

@Eschon
Copy link
Author

Eschon commented Jul 10, 2015

@steelbrain Did that recently because of my problems in Linter/#650 and still get the same deprecation warning.

@steelbrain
Copy link
Contributor

The file produces that error doesn't even exist :P

@Eschon
Copy link
Author

Eschon commented Jul 10, 2015

When I click on the file names in the Deprecation cop it opens a file for me so at least it exists in my linter-jshint installation.

@steelbrain
Copy link
Contributor

Which file does it open? main.coffee?

@batjko
Copy link

batjko commented Jul 10, 2015

@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

@batjko
Copy link

batjko commented Jul 10, 2015

Also I am getting the same issue for some of the other linter-xxx sub-packages.
Looks like the deprecation is actually on the Linter itself.

@steelbrain
Copy link
Contributor

What if I told you that the file it's requiring doesn't even exist, can someone post ls results of

ls ~/.atom/packages/linter-jshint/lib

@batjko
Copy link

batjko commented Jul 10, 2015

@steelbrain Check my comment above.

@steelbrain
Copy link
Contributor

I actually wrote the code there that's reporting the deprecations 😅
There's no deprecation in linter itself, but it reports whenever it tries to require a package like the legacy API.

@Eschon
Copy link
Author

Eschon commented Jul 10, 2015

ls ~/.atom/packages/linter-jshint/lib gives me init.coffee and linter-jshint.coffe
But as @batjko said the first line of the deprecation warning points to ~/.atom/packages/linter/lib/main.coffee not ~/.atom/packages/linter-jshint/lib/main.coffee

@steelbrain
Copy link
Contributor

I can't believe I did this Hahaha, I had upgraded this package to the latest API but haven't published a release yet. 🤦

@steelbrain
Copy link
Contributor

Just pushed a release people, Enjoy.

@Eschon
Copy link
Author

Eschon commented Jul 10, 2015

Well we're all humans 😆
Deprecation is gone now.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants