{"action":"created","issue":{"url":"https://api.github.com/repos/EmergingTechnologyAdvisors/node-serialport/issues/932","repository_url":"https://api.github.com/repos/EmergingTechnologyAdvisors/node-serialport","labels_url":"https://api.github.com/repos/EmergingTechnologyAdvisors/node-serialport/issues/932/labels{/name}","comments_url":"https://api.github.com/repos/EmergingTechnologyAdvisors/node-serialport/issues/932/comments","events_url":"https://api.github.com/repos/EmergingTechnologyAdvisors/node-serialport/issues/932/events","html_url":"https://github.com/EmergingTechnologyAdvisors/node-serialport/issues/932","id":177216791,"number":932,"title":"5.0.0-beta1 - parser with regex support missing","user":{"login":"jupe","id":3822425,"avatar_url":"https://avatars.githubusercontent.com/u/3822425?v=3","gravatar_id":"","url":"https://api.github.com/users/jupe","html_url":"https://github.com/jupe","followers_url":"https://api.github.com/users/jupe/followers","following_url":"https://api.github.com/users/jupe/following{/other_user}","gists_url":"https://api.github.com/users/jupe/gists{/gist_id}","starred_url":"https://api.github.com/users/jupe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jupe/subscriptions","organizations_url":"https://api.github.com/users/jupe/orgs","repos_url":"https://api.github.com/users/jupe/repos","events_url":"https://api.github.com/users/jupe/events{/privacy}","received_events_url":"https://api.github.com/users/jupe/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-09-15T15:57:44Z","updated_at":"2016-09-20T15:49:19Z","closed_at":null,"body":"SerialPort version: 5.0.0-beta1\r\n\r\n### Summary of Problem\r\nprevious release 4.0.1 allow to use [readline](https://github.com/EmergingTechnologyAdvisors/node-serialport/blob/4.0.1/lib/parsers.js#L12) parser with regex delimiter, but seems that it is not possible anymore. It would be useful in some cases where delimiter is not \"hardcoded\" string. For example one of my application uses delimiter `/\\r\\n|\\n\\r|\\n|\\r/` which eats all _carriage return_ (`CR`) and _line feed_ (`LF`) characters away in what ever order they come.. \r\n\r\nThat was \"undocumented feature\" I think, but actually it was very useful :).\r\nIt shouldn't be hard to further develop DelimiterParser a bit to use regex instead of string..\r\n\r\n### Expected Behavior\r\npossible to use DelimiterParser with regex\r\n\r\n### Actual Behavior\r\nregex delimiter is not possible to use"},"comment":{"url":"https://api.github.com/repos/EmergingTechnologyAdvisors/node-serialport/issues/comments/248343543","html_url":"https://github.com/EmergingTechnologyAdvisors/node-serialport/issues/932#issuecomment-248343543","issue_url":"https://api.github.com/repos/EmergingTechnologyAdvisors/node-serialport/issues/932","id":248343543,"user":{"login":"reconbot","id":25966,"avatar_url":"https://avatars.githubusercontent.com/u/25966?v=3","gravatar_id":"","url":"https://api.github.com/users/reconbot","html_url":"https://github.com/reconbot","followers_url":"https://api.github.com/users/reconbot/followers","following_url":"https://api.github.com/users/reconbot/following{/other_user}","gists_url":"https://api.github.com/users/reconbot/gists{/gist_id}","starred_url":"https://api.github.com/users/reconbot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/reconbot/subscriptions","organizations_url":"https://api.github.com/users/reconbot/orgs","repos_url":"https://api.github.com/users/reconbot/repos","events_url":"https://api.github.com/users/reconbot/events{/privacy}","received_events_url":"https://api.github.com/users/reconbot/received_events","type":"User","site_admin":false},"created_at":"2016-09-20T15:49:19Z","updated_at":"2016-09-20T15:49:19Z","body":"100% agreed. I was thinking maybe a transform stream that takes a function to do it's dirty work? Like something you'd pass to `array.reduce`?"}}
{"actor":{"display_login":"reconbot"}}