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

Package.getActivationCommands is deprecated. #88

Closed
rayjanwilson opened this issue May 8, 2015 · 2 comments
Closed

Package.getActivationCommands is deprecated. #88

rayjanwilson opened this issue May 8, 2015 · 2 comments

Comments

@rayjanwilson
Copy link

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 (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:810:9)
Package.hasActivationCommands (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:735:20)
<unknown> (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:189:24)
Package.measure (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:167:15)
@avdg
Copy link
Contributor

avdg commented May 8, 2015

The issues below are still open but should be fixed by 619308e, which is released in 0.1.3:

https://github.com/AtomLinter/linter-jshint/issues?utf8=%E2%9C%93&q=is%3Aissue+is%3Aopen+Package.getActivationCommands+OR+Package.activateConfig

They can all be closed as they are fixed in pr #71

@iam4x iam4x closed this as completed May 9, 2015
@Arcanemagus
Copy link
Member

Duplicate of #60.

@Arcanemagus Arcanemagus added Duplicate and removed Bug labels Sep 26, 2016
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

4 participants