Roadmap #746

Closed
reconbot opened this Issue Apr 8, 2016 · 4 comments

Comments

1 participant
@reconbot
Collaborator

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

  • Cleanup flow control flags #819
  • Throw errors during construction instead of doing them in a zalgo infested callback #820
  • Stop removing registered event handlers ever #764
  • Move the openImmediately argument to options #809,
  • Explore a Streams interface either as a primary or additional interface #832
  • Cleanup the bindings layer #738
  • Support chrome.serialport #739
  • Fix the disconnect behavior #702
  • Explore the whatwg serial api
  • Reconnect options
  • Reading RTS and CTS or having events #291
  • Your hopes and dreams here

@reconbot reconbot referenced this issue Apr 10, 2016

Closed

SerialPort Streams2 Implementation #431

9 of 10 tasks complete

@reconbot reconbot changed the title from Roadmap to 3.0 to Roadmap Apr 16, 2016

@reconbot

This comment has been minimized.

Show comment
Hide comment
@reconbot

reconbot Apr 16, 2016

Collaborator

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.

Collaborator

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

This comment has been minimized.

Show comment
Hide comment
@reconbot

reconbot May 23, 2016

Collaborator

I put together a shortlist for 4.0

Collaborator

reconbot commented May 23, 2016

I put together a shortlist for 4.0

@reconbot

This comment has been minimized.

Show comment
Hide comment
@reconbot

reconbot Jul 29, 2016

Collaborator

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

Collaborator

reconbot commented Jul 29, 2016

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

@reconbot

This comment has been minimized.

Show comment
Hide comment
@reconbot

reconbot Jul 16, 2017

Collaborator

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

Collaborator

reconbot commented Jul 16, 2017

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

@reconbot reconbot closed this Jul 16, 2017

@node-serialport node-serialport 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.