You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Atom will no longer load this package after June 1st without changes. There are a couple deprecations on the latest version (0.2.3) of this package:
Use activationCommands instead of activationEvents in your package.json Commands should be grouped by selector as follows: json "activationCommands": { "atom-workspace": ["foo:bar", "foo:baz"], "atom-text-editor": ["foo:quux"] }
Store package style sheets in the styles/ directory instead of stylesheets/ in the <pack-name> package
atom.workspaceView is no longer available. In most cases you will not need the view. See the Workspace docs for alternatives: https://atom.io/docs/api/latest/Workspace. If you do need the view, please use atom.views.getView(atom.workspace), which returns an HTMLElement.
@benogle is the package currently "not working" because of the deprecations? I just cloned this into my packages directory and none of the shortcuts work; however, I'm not sure if it's because of this issue or if I should open a new issue. Thanks 😀
Atom will no longer load this package after June 1st without changes. There are a couple deprecations on the latest version (
0.2.3
) of this package:activationCommands
instead ofactivationEvents
in your package.json Commands should be grouped by selector as follows:json "activationCommands": { "atom-workspace": ["foo:bar", "foo:baz"], "atom-text-editor": ["foo:quux"] }
styles/
directory instead ofstylesheets/
in the<pack-name>
packageatom.views.getView(atom.workspace)
, which returns an HTMLElement.Visit https://gist.github.com/benogle/6d09e295c84b717ef9b4 and search for your package name to see up-to-date deprecations.
If this package has been replaced by another package or functionality in core, please reply with this information.
See atom/atom#6867 for more info. Thanks!
The text was updated successfully, but these errors were encountered: