42
Cloudflare outage due to excessive useEffect API calls
(blog.cloudflare.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 14 Sep 2025
42 points (100.0% liked)
Programming
28322 readers
767 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 3 years ago
MODERATORS
/* eslint-disable-next-line specific-rule-name */Only for multiline comment delimiters
I guess that's a tad better, though if the rule is named
react-hooks/exhaustive-depsthen we're still not explaining why we're disabling it.What I'm really looking for is something that explicitly tells the programmer/code reader "this blows up into an infinite loop if we respect exhaustive deps, but here we don't need exhaustive deps for the code to be sound".
My own, hair-baked proposal: have the linter recognize
[foo, baz /*, @causes-infinite-loop bar */](or something along those lines) as an explicit, programmer-validated escape hatch for not respecting theexhaustive-depsrule.After the rule name you can add a free text explaining the reasons
Oh nice, I always thought that was for disabling multiple rules with a single line. Cheers!
Im saving all these for when I might use react again