cache: over-eager caching of results from custom rules
See original GitHub issueTell us about your environment
- ESLint Version:
5.8.0
- Node Version:
nightly
- npm Version:
N/A
What parser (default, Babel-ESLint, etc.) are you using? default
Please show your full configuration: https://github.com/nodejs/node/blob/master/.eslintrc.js
What did you do? Please include the actual source code causing the issue, as well as the command that you used to run ESLint.
I have a custom rule that depends on the content of a third file Refs: https://github.com/eslint/eslint/pull/10571#issuecomment-436416417
node tools/node_modules/eslint/bin/eslint.js --cache --ext=.js,.mjs,.md lib\internal\error.js
What did you expect to happen? linter should apply rules if dependencies change.
What actually happened? Please include the actual, raw output from ESLint. linter used cached results
Are you willing to submit a pull request to fix this bug? Of Course
Issue Analytics
- State:
- Created 5 years ago
- Reactions:1
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Introducing Cache Rules: precision caching at your fingertips
Cache Rules allows users to set caching behavior on additional criteria, such as the HTTP request headers or the requested file type.
Read more >Configuring the Apollo Client cache - Apollo GraphQL Docs
This article describes cache setup and configuration. To learn how to interact with cached data, see Reading and writing data to the cache....
Read more >Control Azure CDN caching behavior with caching rules
Custom caching rules match specific paths and file extensions, are processed in order, and override the global caching rule, if set.
Read more >Cache Settings - Imperva Documentation Portal
Create custom cache rules. Custom cache rules let you define specific exceptions to the caching rules that are set by the overall Cache...
Read more >Caching - Akamai TechDocs
You can enable Enhanced RFC support that lets you honor additional Cache-Control header directives from the origin. The directives adhere to RFC-standards, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
The ESLint team has just created an RFC process for complicated changes that require designs. This issue was marked as “needs design” and so falls into this new RFC process. You can read more about the RFC process here:
https://github.com/eslint/rfcs/
Thanks!
Unfortunately, it looks like there wasn’t enough interest from the team or community to implement this change. While we wish we’d be able to accommodate everyone’s requests, we do need to prioritize. We’ve found that issues failing to reach accepted status after 21 days tend to never be accepted, and as such, we close those issues. This doesn’t mean the idea isn’t interesting or useful, just that it’s not something the team can commit to.
Thanks for contributing to ESLint and we appreciate your understanding.