Deprecated Atom APIs will be removed June 1st

[benogle]

Atom will no longer load this package after June 1st without changes. There are a couple deprecations on the latest version (0.2.0) of this package:

1. 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"] }
2. Store package style sheets in the styles/ directory instead of stylesheets/ in the <pack-name> package
3. 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.
4. Requiring View from atom is no longer supported. Please require atom-space-pen-views instead: {View} = require 'atom-space-pen-views' Add "atom-space-pen-views": "^2.0.3" to your package dependencies.

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 https://github.com/atom/atom/issues/6867 for more info. Thanks!

[braincomb]

@mojombo any plans to update this package to work with Atom 1.x?

[MatthewSH]

@benogle This may be quite late, however...I just happened to find this package and I'm considering forking and updating it for Atom.

[mixolidia]

@mojombo update this package please 😊🙏🏾

[filipef101]

BUMP

[mojombo]

First person to volunteer gets commit access to bring this up to date.

[MatthewSH]

@mojombo I mean, I could probably look more into it if you want...don’t get me commit access...if I have a free moment this week while on vacation I’ll be happy to at least tinker on a fork.

[filipef101]

There are no changes in the atom API that make this not possible anymore then? @benogle @mojombo

[MatthewSH]

@filipef101 I’m really really really trying to understand the point you’re trying to make, but I can’t. So do you think you can reword that? It seems contradictory.

[filipef101]

Sorry for that. I mean, I tought that this package/game was no longer possible to implement due to API changes. It is possible to make this work again right? No API changes break the possibility of having this work again?

[MatthewSH]

You’re fine, thanks for the clarification. There should be documentation about alternative API calls that could be made. Like I said, if I get the time this week I’ll be more than happy to look into it.