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

Triggers deprecation warnings in atom > 0.190 #8

Closed
idan opened this issue Apr 20, 2015 · 0 comments
Closed

Triggers deprecation warnings in atom > 0.190 #8

idan opened this issue Apr 20, 2015 · 0 comments
Labels

Comments

@idan
Copy link

idan commented Apr 20, 2015

See [https://github.com/atom/atom/issues/6310] for more context

Use a config schema instead. See the configuration section of https://atom.io/docs/latest/hacking-atom-package-word-count and https://atom.io/docs/api/latest/Config for more details
Called 1 time
Package.activateConfig - /Applications/Atom.app/Contents/Resources/app/src/package.js:247:11
Package.activateNow - /Applications/Atom.app/Contents/Resources/app/src/package.js:218:14
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"]
  }
Called 1 time
Package.getActivationCommands - /Applications/Atom.app/Contents/Resources/app/src/package.js:766:9
Package.hasActivationCommands - /Applications/Atom.app/Contents/Resources/app/src/package.js:691:20
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants