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

Package.activateConfig is deprecated. #59

Closed
d4k0 opened this issue Apr 9, 2015 · 0 comments
Closed

Package.activateConfig is deprecated. #59

d4k0 opened this issue Apr 9, 2015 · 0 comments
Labels
Bug

Comments

@d4k0
Copy link
Contributor

d4k0 commented Apr 9, 2015

This deprecation message appears since Atom 0.189.0:

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

Package.activateConfig (D:\Programme\Dokumente\Atom\resources\app\src\package.js:250:11)
Package.activateNow (D:\Programme\Dokumente\Atom\resources\app\src\package.js:221:14)
d4k0 pushed a commit to d4k0/linter-jshint that referenced this issue May 3, 2015
This should fix AtomLinter#60/AtomLinter#67/AtomLinter#68 and AtomLin…
619308e 
…ter#59/AtomLinter#66, i. e. "Package.getActivationCommands is deprecated" and "Package.activateConfig is deprecated".
iam4x pushed a commit that referenced this issue May 4, 2015
Merge pull request #71 from d4k0/master
9ae5b52 
This should fix #60/#67/#68 and #59/#66, i. e. "Package.getActivationCom...
@iam4x iam4x closed this as completed May 4, 2015
This was referenced Sep 26, 2016
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Arcanemagus @iam4x @d4k0