Stop parsing

[tobiasrichter]

It would be great to allow stop parsing in record_parsed. In case of searching some value it would useful stop that after obtaining satisfied values.

[Keyang]

Hi, If you are stream / pipe, you can simply unpipe the parser from readable stream. ~Keyang

…

On 19 December 2016 at 10:29, tobiasrichter ***@***.***> wrote: It would be great to allow stop parsing in record_parsed. In case of searching some value it would useful stop that after obtaining satisfied values. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#127>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABCs98moRi6eld6Oz3RnvKup1oZ1luDlks5rJlx-gaJpZM4LQk8r> .

[dmitry-dulevich]

@Keyang hey. You didn't left function to stop parsing. Your answer does not work with Strings.

[Keyang]

Hi @dozen1488 , there is a difference between "stop parsing" and "stop emitting".
If stream is the csv source, data streaming will stop as soon as unpipe thus parser will "stop parsing" immediately
if source is csv string, data parsing has finished before emitting first line of json -- it will convert whole csv data together.

However, neither of the situation above means parser will "stop emitting" immediately if there are still "parsed" csv data not emitted in parser. And this does not consume CPU as all "heavy parsing" has already being done.

If you do want to "stop emitting" under some condition, you can do this easily:

const csv=require('csvtojson')
const conv=csv()
.fromString(csvString)
.on('json',(json)=>{
  if (<somecondition meets>){
    conv.off('json') // unsubscribe json event 
  }
})

[dmitry-dulevich]

@Keyang thanks for responding. Probably you meaned 'conv.removeAllListeners'. It works now

[pradeeptimeinc]

@here getting conv.off is not a function when trying conv.off('json');

[Keyang]

@pradeeptimeinc see @dozen1488 comment it should be:

const csv=require('csvtojson')
const conv=csv()
.fromString(csvString)
.on('json',(json)=>{
  if (<somecondition meets>){
    conv. removeAllListeners('json') // unsubscribe json event 
  }
})

[pradeeptimeinc]

@Keyang thanks and one more thing how can i throw from

.on('json',(obje)=>{
    //throw some err
})
.on('error',(error)=>{
    // catch it here
})

[Keyang]

you can call

.on('json',(obje)=>{
    conv.emit('error', errObj)
})
.on('error',(error)=>{
    // catch it here
})

[pradeeptimeinc]

@Keyang thanks 👍 👍

[sarathsaleem]

Even after
conv.emit('done', { 'done': true });
or
conv.emit('end', { 'done': true }); the process is not being exited.

[Keyang]

Im not sure what you mean by the process is not being exited. If a node.js process is hanging, it means it's either opened some sockets / files without closing them or event loop is not cleared.

[sarathsaleem]

I have a write stream created for that so I have to exit the process manually along with conv.emit('end', {}); process.exit() , I think it should be in this way .. so not any issue with events

[Keyang]

Close due to no activity