Martin Hansen

It was probably a mistake to call it 2.0 The functionally for this plugin was the same but due to major refactoring and peer dependency of inquirer v8 I versioned...

+1

I also has this problem on 7.51.1 , not on 7.51.0. Additionally if using nested fields the validatingFields looks like this: rootprop deep.nested.prop Then validatingfields look like: ``` { rootprop:...

Does this have anything to do with devtools? I do not use the devtools and get a similar error.

+1 but suspect it's hard to do. Currently I'm not using open because of this.

I would at least still appreciate #42. What @kaidokert mentioned, inserting into paths like grunt-bower-requirejs does would be nice. Btw, both this project and that project uses the bower property...

Yeah that should have been handled better. In the newer `inquirer-autocomplete-standalone` package it is handled and presented as an error if it fails. 

Not sure why I never implemented that, I guess I never had the problem myself so forgot/ignored, and nobody else mentioned it either until now :)

Sure that could be useful, if you decide to do it you should also add it for searchText then at the same time I think. And the function should probably...

Thanks for reporting! I must have not tested this properly: https://github.com/mokkabonna/json-schema-merge-allof/pull/2 Should have left it as it was.