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

Package.getActivationCommands is deprecated. #21

Closed
zetay opened this issue May 4, 2015 · 1 comment
Closed

Package.getActivationCommands is deprecated. #21

zetay opened this issue May 4, 2015 · 1 comment

Comments

@zetay
Copy link

zetay commented May 4, 2015

atom -v 0.196.0
Use activationCommands instead of activationEvents in your package.json
Commands should be grouped by selector as follows:

  "activationCommands": {
    "atom-workspace": ["foo:bar", "foo:baz"],
    "atom-text-editor": ["foo:quux"]
  }
Package.getActivationCommands (D:\GreenSoft\Atom\resources\app.asar\src\package.js:790:9)
Package.hasActivationCommands (D:\GreenSoft\Atom\resources\app.asar\src\package.js:715:20)
<unknown> (D:\GreenSoft\Atom\resources\app.asar\src\package.js:169:24)
Package.measure (D:\GreenSoft\Atom\resources\app.asar\src\package.js:147:15)
@kevinsawicki
Copy link
Member

This was fixed by adf33cd and will go away if you upgrade to the latest version, 0.0.16 or above.

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

No branches or pull requests

3 participants