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

Package.getActivationCommands is deprecated. #13

Closed
d4k0 opened this issue Apr 9, 2015 · 1 comment
Closed

Package.getActivationCommands is deprecated. #13

d4k0 opened this issue Apr 9, 2015 · 1 comment

Comments

@d4k0
Copy link
Contributor

d4k0 commented Apr 9, 2015

This deprecation message appears since Atom 0.189.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:\Programme\Dokumente\Atom\resources\app\src\package.js:764:9)
Package.hasActivationCommands (D:\Programme\Dokumente\Atom\resources\app\src\package.js:689:20)
d4k0 pushed a commit to d4k0/linter-htmlhint that referenced this issue May 3, 2015
…"Package.activateConfig is deprecated" and "Package.getActivationCommands is deprecated".
johnwebbcole added a commit that referenced this issue May 4, 2015
This should fix #12/#16 and #13, i. e. "Package.activateConfig is deprec...
@kevinsawicki
Copy link
Member

This was fixed by #19

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