Currently working on #3611 Glob based configuration <https://github.com/eslint/eslint/issues/3611>, and specifically making cacheing work. I noticed config files are cached in config.localConfigFinder / FileFinder, but not the config contents. This makes a little sense since merged directory configs are cached, but it's also a weird since incremental cacheing is not utilized (i.e., traverse up config hierarchy to nearest cache and merge from there; e.g., a/b is cached, a/b/c is not, but config hierarchy is merged from scratch instead of from a/b's cache).
Is there a reason not to do this? I see none. The seemingly negligible memory overhead of cacheing config files (since we're already cacheing merged directory configs), seems more than worth the performance gains to be had by not having to reload from fs and recompute (extends, plugins, etc...) config files. -- You received this message because you are subscribed to the Google Groups "ESLint" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
