This is a minimal-invasive change that effectively makes the execution of filters asynchronous by using promises. The change allows the use of filter (not) exist in any combination with other filters and at any depth within filter expressions.
The promises are implemented by using the 'es6-promise' module.
This is a fix for the issue #125.
I will also add some tests when I have some time to do it.
Is this of any interest?
If this is the case then I'm happy to prepare a mergeable PR without conflicts based on the latest HEAD revision.
Any comments are welcome.
This is a minimal-invasive change that effectively makes the execution of filters asynchronous by using promises. The change allows the use of filter (not) exist in any combination with other filters and at any depth within filter expressions. The promises are implemented by using the 'es6-promise' module.
This is a fix for the issue #125.
I will also add some tests when I have some time to do it.