chris-pardy

@CacheControl my thought on this is that we could make the `Condition` constructor pluggable, so that it's easy to drop in custom condition classes. Additionally a way to plug in...

@CacheControl see #356 for part of the work to support something like this. The ability to plug in custom condition classes in order to add arbitrary logic. In this case...

@dcowan-e-courier can you check which version of `hash-it` you have installed?

@siawyoung @dcowan-e-courier this does seem to be related to the export mapping on the `hash-it` package and how something like webpack is resolving that.

@MohHamoud I haven't reproduced this issue since it's more related to webpack than json-rules-engine but... The issue is likely that the webpack version that create-react-app is using doesn't understand the...

@MohHamoud this makes sense since we transform the source from modules to common / require. As part of that babel is doing a default import transformation. Then the webpack resolution...

@mjaniko @jyothis-qb I would need to see the actual rules to get a sense for exactly the cause. However I can say that if you're using JSON path expressions to...

@JeffrinCh Again I would need to see a specific example to understand exactly but if you're using the `path` attribute you're going to experience some drop in performance as the...

@jyothis-qb @JeffrinCh I did some digging and here's my suggestions: This shows a comparison of runtime across 10,000 executions of calling `Almanac.factValue` on a fresh `Almanac` instance so no caching...

@CacheControl I also did some digging / profiling of jsonpath-plus and it does seem to be very very optimized. It already caches the results of compiling a path into a...