Closed benogle closed 9 years ago
I just updated coffee-autocompile to be compatible with the new API :) It's 224 on the list.
@olmokramer Thanks! :heart:
@adrianolaru, @Kraoz, @hirohisa, @urecio, @PierreVannier, @cliffrowley, @rGalrito, @Levia, @forabi, @yezhiming, @skandasoft, @davidlgoldberg, @mendab1e, @darkhelmet, @laktak, @thomasjo, @iambald, @adambutler, @rockymadden, @noraesae, @DanBrooker, @jackytsu, @jhonaker, @cabaag, @unitjs, @malexandre, @nickstark, @forivall, @destradax, @sidorares, @manuclementz, @asciidoctor, @jedahan, @garralab, @robhurring, @kmorey, @akaytatsu, @SKAhack, @oggy, @jbrains, @camel-chased, @merrihew, @james2doyle, @numso, @lloeki, @lierdakil, @MindscapeHQ, @leny, @amesarosh, @VoiceCode, @maprinz, @RYTong, @Raynes,
@angular-ui, @JsonHunt, @Frozenfire92, @jefkoslowski, @131, @f1nnix, @deusanyjunior, @varyform, @m1ga, @siddiq, @cs150bf, @kieranju, @carlosingles, @alexcorre, @ignaciocases, @casesandberg, @sedabull, @abe33, @jtokoph, @probablycorey, @hmatsuda, @smashwilson, @prozacchiwawa, @Trudko, @maxxcrawford, @oredon, @orlaqp, @iraasta, @diiq, @Freyskeyd, @burntime, @Galadirith, @karan, @radicaled, @iori-o, @mh61503891, @harada4atsushi, @griffin-stewie, @shm, @Alchiadus, @mafiuss, @jonahss, @zhuochun, @lee-dohm, @alexchee, @t9md, @eddieantonio, @indiejames, @romgrk, @herkulano, @papermoon1978, @justinkelly
unsubscribe
Jayson Jacobs
Instagram: @jayssface http://instagram.com/jayssface Twitter: @jayssface http://twitter.com/jayssface USA Cycling http://www.usacycling.org/results/?compid=310968
On Wed, May 20, 2015 at 2:18 PM, Ben Ogle notifications@github.com wrote:
/cc @mgrenier https://github.com/mgrenier, @yasuyuky https://github.com/yasuyuky, @sscotth https://github.com/sscotth, @brentd https://github.com/brentd, @kenokabe https://github.com/kenokabe, @vellerefond https://github.com/vellerefond, @bsnux https://github.com/bsnux, @francodacosta https://github.com/francodacosta, @iancmyers https://github.com/iancmyers, @rpowelll https://github.com/rpowelll, @postcasio https://github.com/postcasio, @bigfive https://github.com/bigfive, @mattberkowitz https://github.com/mattberkowitz, @emmetio, @baconscript, @Problematic https://github.com/Problematic, @dmackerman https://github.com/dmackerman, @raviraa https://github.com/raviraa, @RokkinCat https://github.com/RokkinCat, @thomaslindstrom https://github.com/thomaslindstrom, @tulios https://github.com/tulios, @gstack https://github.com/gstack, @anaptfox https://github.com/anaptfox, @tarnfeld https://github.com/tarnfeld, @Trudko https://github.com/Trudko, @CentaurWarchief https://github.com/CentaurWarchief, @p-e-w https://github.com/p-e-w, @amoussard https:/%20/github.com/amoussard, @rgbkrk https://github.com/rgbkrk, @benastan https://github.com/benastan
— Reply to this email directly or view it on GitHub https://github.com/atom/atom/issues/6867#issuecomment-103982877.
Awww, you caught me. Is there a way to deprecate my python
package (or redirect) in favor of script?
Hi. Thanks for the heads-up. I'm eagerly awaiting for data on specific deprecations, since I couldn't find anything outstanding on my own (I've fixed what I've found atm, but more info would be great)
As a side note, language-haskell
seems abandoned to me, since there is no activity in the repo since Oct 2014. I'll try to reach out to @jroesch to see if he would be willing to transfer package ownership.
@benogle thanks for the heads up. I'll work on updating the API Blueprint preview plugin soon, but have a question - is there a plugin like AtomLinter yet that takes plugins for live preview? It would be nice not to have to copy and track the GFM preview plugin just to run an external tool and display the output in a window.
EDIT: Fairly sure remember-session is supplanted by the 198 re-open last project feature.
Some of those offer functionalities which should be in core, for instance: synced-sidebar error-status minimap-color-highlight selection-count omni-ruler
Some of those offer functionalities which should be in core, for instance
Without addressing the question of whether they should or shouldn't be in core, it's a fact that they won't be in core before deprecated APIs are removed.
@danielgtaylor:
is there a plugin like AtomLinter yet that takes plugins for live preview?
@lee-dohm suggested something like this in #6817 - were it to be implemented it would probably use the Services API like autocomplete-plus, etc, but it doesn't exist yet.
Nice catch, the debugger is work in progress
I currently don't get any depreciations in 0.200.0 for autoclose-html, but when there are updates about specific depreciations I'll get on them.
@rgbkrk yes, we will have a way to deprecate packages. Thanks for the heads up.
@lierdakil looks like you may have fixed it. There was one deprecation from ac-haskell: getEditors
, which looks to be now using getTextEditors
. Also thanks for taking the reins on language-haskell :+1:
@mattberkowitz autoclose-html@0.16.0 looks like it has the following:
atom.views.getView(atom.workspace)
, which returns an HTMLElement. callNow
option. Use ::onDidChange instead. Note that ::onDidChange passes its callback different arguments. See https://atom.io/docs/api/latest/Config @mattberkowitz hmm. Looks like I get no deprecations either when I install autoclose-html. Looks like you're using workspaceView in the specs, but thats it.
@benogle I'll drop the specs, pretty sure they're autogen from way back when anyway. I definitely updated to the new config schema/apis in 0.16.0 so not sure where those are coming from. (4) might be related to atom.workspace.observeTextEditors
the message doesn't offer much clarity?
@benogle, I also happen to maintain haskell-ghc-mod
and ide-haskell
, those two pose greater challenge in tracking down deprecations, especially the latter. I see none when using those normally, but apparently, there are some, probably lurking in rarely-executed code. If you could get data on those, that'd be tremendous. Thanks again.
@lierdakil Looks like there are a couple deps in each of those haskell packages
Here is an export of the deprecation messages associated with each package / version https://gist.github.com/benogle/6d09e295c84b717ef9b4
Please remove open-terminal-here and show-in-folder. I've abandoned them. I would have done it myself but you don't offer the option to remove from the marketplace.
@Flynsarmy and anyone else, you can run apm unpublish <package-name>
to remove packages
[atom (master)]> apm help unpublish
Usage: apm unpublish [<package_name>]
apm unpublish <package_name>@<package_version>
Remove a published package or package version from the atom.io registry.
The package in the current working directory will be used if no package
name is specified.
Options:
--help, -h Print this usage message
--force, -f Do not prompt for confirmation [boolean]
Prefix an option with `no-` to set it to false such as --no-color to disable
colored output.
@Flynsarmy you can do apm unpublish
like I did.
Updated, thanks for the heads up!
Thanks. Unpublished
updated! thanks for the info!
@benogle, thank you!
I updated haskell-ghc-mod
. It was rather obvious, but I somehow missed it.
ide-haskell
doesn't seem to need updating, however. As of 0.4.0, it uses config schema, and getRootDirectory
was fixed back when it was deprecated in the first place. Should I assume those are false positives from older versions?
Fixed, published.
Thank you to everyone who is updating their packages, especially to @rjfranco for the sweet gif.
Looks like there are a few false positives in the analytics data. Sorry about that, and I'm working to understand/fix them.
Edit: false positives can happen when a package is updated. At this time, if your package has deprecations on 0.3.0, then you fix and release them in 0.4.0. The user upgrades and the reporter attributes 0.3.0 deprecations to 0.4.0. This will be fixed in the next version of atom.
Fixed
I've unpublished my package, it was merged a while ago in to bracket-matcher, I just never got round to removing it.
I've unpublished atom-angularjs, it merged AngularJS-Atom.
I've stopped using the deprecated open-end transaction APIs. https://github.com/yasuyuky/autocomplete-clang/commit/95470cd2fcafe806f6f19024aff0ed065549c3d3 Thanks.
I've unpublished language-jsx for React-JSX people, our JSX is here. But the name leads misunderstandings...
https://github.com/jacogr/atom-git-control fixed, waiting for final tests & approval to make apm release, https://github.com/jacogr/atom-gulp-control updated to 0.4.0 that addresses all issues
@goddardc I see that you've deleted the repo for recent-files, but the package is still published on atom.io which will cause some errors. If I remember right you may not be able to apm unpublish
it now – /cc @thedaniel?
For other package authors, please apm unpublish
everything before you start deleting repos!
Didn't realize that. Sorry! If there's anything I can do, let me know.
Guys, green tick for @CentaurWarchief/autocomplete-PHPUnit, @arandilopez did it in autocomplete-PHPUnit/pull/6. Should I update something else?
@benogle the API Blueprint Preview plugin is up to date now. It's number 113 in your table.
Alright, gist-it should be all good as of 0.7.0.
I just fixed Coverage (Position 148) :+1:
@benogle I just updated remote-sync (Position 11)
@benogle Good to go on all 3
I've just updated atom-jshint (position 4). That got out of hand, really hoping I havn't broken something!
Great work on the deprecation cop though, worked a charm!
I just unpublished background-matrix
Opened lloeki/ex-mode#42, but I'm super busy right now.
@benogle Published deprecation fix for atom-jade
I've updated the table with the top 300 from the most recent analytics and atom.io data. This data should not have false positives, and should have removed the packages that have been upgraded. Note that it is 24 hours of data generated by users who upgraded to 0.201, so the user counts are low, and it may not contain everything. I will update it again in the next couple days.
Thank you again to all y'all who are updating their packages. You are helping make the upgrade experience a lot better. :yellow_heart: :heart: :green_heart: :blue_heart:
language-typescript is dead, feel free to just unpublish (atom-typescript should be used instead)
@benogle I was rushing to release color-picker
v2.0.0
as soon as possible to fix any of the deprecations, here, seeing as it was reported in the table. But now it's disappeared from the table data, and I haven't really done anything about it – what happened?
@thomaslindstrom Interestingly, as a user of color-picker
(Great work on that by the way), there are no deprecation warnings in it with the latest Atom release. Apparently it's all good! (color-picker
1.7.0
)
@thomaslindstrom there were false positives in the last dataset. Basically if your package had deprecations on 1.6.0, then you fixed them and released 1.7.0, then the user upgrades, the reporter would attribute deprecations from 1.6.0 to 1.7.0 until a reload. So the last table may have shown a bunch that were caused by users upgrading to the non-depreacted version.
We've been collecting data on which packages have deprecations since 0.201. This is a list of the packages using deprecated APIs, their owners and each package's impact. This data reflects a subset of the user population (those who have upgraded to 201). Affected numbers are based on unique users catching the deprecations.
If you are a maintainer on this list please note that we will be removing deprecated APIs on June 1st. See the blog post for more info. Note that upgrading to the new APIs will decrease breakage, increase speed, and generally be better for everyone.
Upgrading your package
We have a few guides for upgrading your package or theme:
View
class rather than importing them from atom. See the package upgrade guide for details.Need help upgrading?
The community and the core team can offer some help:
Package abandoned?
If your package is abandoned or supplanted by something in core, please comment with the package name and we can take steps to remove it from the package listing and people's install.
However, _do not delete the package repo from GitHub before unpublishing_, as this will make it so that you can't unpublish from the package registry.
Notes
Generated: Wed Jun 03 2015 18:15:00 GMT-0700 (PDT)