-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update plugin to new provider service #141
Comments
Nuclide does tuesday releases (internally and open-source), so if you publish the new tool-bar on Monday morning, then that gives me a day to update. This would be the ideal case. |
I'm going to hold of publishing for a little bit. This issue was opened to get a list of plugins using the tool-bar API and informing them of the changes before releasing the package. The list was summarized out of the top of my head, but requires some more research. The idea right now is to update the list, at least informing the package authors and maybe sending an PR. |
Can someone confirm that using |
Yeah... require('semver').toComparators('^0 || ^1')
// [ [ '>=0.0.0', '<1.0.0' ], [ '>=1.0.0', '<2.0.0' ] ] |
Thanks for the confirmation on the ranges. Some explanation. Previously we had |
Yup. See https://github.com/npm/node-semver#caret-ranges-123-025-004
|
Because of the very hard work and if you agree, I like you to add to the list of contributors on the readme. In #140 (comment) you mentioned that there is room for improvements and performance. I'm especially interested in your thoughts about performance improvements. |
Thanks @jerone! 😄 |
@jerone as far as perf:
|
|
I resize my window a lot - probably because I'm always opening/closing the devtools. This is easy to fix though.
I'm only concerted with batching the DOM updates during the Atom package activation cycle. We put 13 buttons on the tool-bar - that's a lot of redrawing. I'm on a mission to reduce start up time :) |
Any word on publishing the space-view-less update? |
@zertosh commented on 8 jun. 2016 23:47 CEST:
Before publishing the package with the awesome new changes we need to contact all plugins (send PR) so they have time to react on the breaking changes. I've already started to research some plugins above, but the list is not yet finished. |
📦 ⬆️ Update tool-bar package provider service. Per atom-community/tool-bar#141
📦 ⬆️ Update tool-bar package provider service. Per atom-community/tool-bar#141
@jerone We're good on my side! Thanks! |
@jerone Sorry, I had no time to do that... 😫😫😫 |
Summary: The `tool-bar` package will soon release v1.0.0. In this update, it has dropped `space-pen`, so `addButton` no longer returns a `space-pen` view. However, it does expose the underlaying DOM element the same way - via an `element` property. This diff changes our `tool-bar` usage to always use `element` (when needed), and sets the service API version requirement to `^0 || ^1` (since this is a backwards-compat change). A lot of packages weren't properly disposing of `tool-bar` related resources. This was most obvious with packages that showed state on `tool-bar` element. If `tool-bar` was disabled, and then re-enabled, the counters would never update. Less obvious was that by subscribing to the cleanup disposable when either the tool-bar or the package was disabled, meant that the other side's disposable still held a reference to the toolbar. See: atom-community/tool-bar#141. Reviewed By: jamesgpearce Differential Revision: D3513888 fbshipit-source-id: f995d3e9c686876d36924054cf1dd2f88e1650a7
Closing, as all plugins have been notified and/or updated. |
@cakecatz Almost 5 months after removing space-pen dependency and switching to ES6, it's time to merge #153 and remove all legacy code. The only thing blocking this is the Flex Toolbar package still running on the old API (most noticeable packages have already switched). Once merged, Flex Toolbar will completely stop working. I noticed you already made an attempt to upgrade on a different branch. Is there any change to speed up this process? /cc @zertosh |
@jerone, we're all good on my end |
@jerone Hi! I pushed commit for support new tool-bar provider just now. |
@cakecatz Great! Do you want me to test? I probably have some spare time tonight. |
@jerone Yes please 🙏 |
@cakecatz commented on 7 sep. 2016 12:15 CEST:
Just tested your latest commit with #153 and it worked with my configuration. Let me know when you released Flex Tool Bar, so I can merge #153. |
@jerone Thanks! |
Hi Jerone. |
I think it's nice to let plugin developers know that there's a new provider service available so we can remove the legacy code as soon as possible. Besides that, the previously documented provider semver won't support the new version we're releasing.
There are two lists of plugins:
List one:
Atom Electric Imp Tools ➡️ Update tool-bar package provider service deldrid1/atom-imp-tools#1List two:
This is a work in progress as there are way more plugins available.List seems complete for the moment.Ref #135, #136, #140.
The text was updated successfully, but these errors were encountered: