Skip to content
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

Roadmap #746

Closed
8 of 11 tasks
reconbot opened this issue Apr 8, 2016 · 4 comments
Closed
8 of 11 tasks

Roadmap #746

reconbot opened this issue Apr 8, 2016 · 4 comments
Labels
feature-request Feature or Enhancement

Comments

@reconbot
Copy link
Member

reconbot commented Apr 8, 2016

I'd like to use this issue to discuss breaking changes to the SerialPort library. 2.0.7 has changed a lot of the internals but left the api largely intact. I'd like to make some goals and address specific api changes.

Internals and APi Changes

@reconbot reconbot changed the title Roadmap to 3.0 Roadmap Apr 16, 2016
@reconbot
Copy link
Member Author

reconbot commented Apr 16, 2016

My current plans involve a 3.0 release that removes the close and disconnect removeAllListeners() calls. These are basically bugs imho, but they are major api changes so 3.0.0. Most everyone will be able to update to 3.0 without any major code changes.

A 4.0 release will take a bit longer and need some discussion. I want to clean up options, and construor apis (eg throw immediatly on config issues, ensure update does the right thing everywhere. And lastly kill the factory. This will also make it a lot easier to have a single disconnect path for windows and everyone else, and isolate the pause/resume functions to the bindings.

@reconbot
Copy link
Member Author

I put together a shortlist for 4.0

@reconbot
Copy link
Member Author

I have a few links to serialport like interfaces that could be potential bindings layers.

@reconbot reconbot added the feature-request Feature or Enhancement label Aug 22, 2016
@reconbot
Copy link
Member Author

Most of these are completed. Gonna close as 5.0 is close to release.

@lock lock bot locked as resolved and limited conversation to collaborators May 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
feature-request Feature or Enhancement
Development

No branches or pull requests

1 participant