search

randy3k / remote-atom

rmate for atom
https://atom.io/packages/remote-atom
MIT License
85 stars 16 forks source link

Package.activateConfig is deprecated. #17

Closed throker closed 9 years ago

throker commented 9 years ago

I got the latest version of both Atom and Remote-Atom installed. You can see a screenshot below. It does still work though. remote-atom deprication

Below is the automated issue text created by Atom

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 (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:247:11)
Package.activateNow (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:218:14)
<unknown> (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:203:30)
Package.measure (/Applications/Atom.app/Contents/Resources/app.asar/src/package.js:147:15)
randy3k commented 9 years ago

I am quite busy these two days. Could you submit a PR? Thanks in advance.

randy3k commented 9 years ago

Fixed now.

throker commented 9 years ago

Thanks randy3k! I don't think I would have been much help since I'm very new to Git. And I also only discovered/installed Atom 2 days ago. I've installed the update and it works fine without any issues.

randy3k commented 9 years ago

It is quite annoying that the atom API changes frequently. 😅