Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

ThemePackage.activateConfig is deprecated. #478

Closed
alexgibson opened this issue Apr 24, 2015 · 1 comment
Closed

ThemePackage.activateConfig is deprecated. #478

alexgibson opened this issue Apr 24, 2015 · 1 comment

Comments

@alexgibson
Copy link

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

ThemePackage.activateConfig (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:247:11)
PackageDetailView.activate (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/settings-view/lib/package-detail-view.js:155:26)
PackageDetailView.updateInstalledState (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/settings-view/lib/package-detail-view.js:193:12)
<unknown> (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/settings-view/lib/package-detail-view.js:222:24)
@izuzak
Copy link
Contributor

izuzak commented Apr 24, 2015

Thanks for the report, @alexgibson -- this looks like a duplicate of #477. There's a problem with how these deprecated calls are attributed to packages -- this should be fixed when atom/atom#6510 is merged and a new Atom version is released. Currently, those calls are incorrectly attributed to Atom core or to the settings view package.

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

2 participants