I could! I'd probably have to take it piece by piece, rather than telling an AI to edit hundreds of files in one epic session and hoping for the best. Even just reviewing a commit that large feels like it would be a bad use of time. Also, giving every variable a type (or using "mixed" everywhere), and giving every function a return type (more "mixed" or "void") would just make the code more verbose without any justification that I can see.
replyWith Zed, I feel like I'm being dragged into a modern style guide that I never agreed to. It would be nicer if I could make it my own by turning off those parts that I disagree with and keeping the rest. I know this is technically possible, but they've certainly not made it easy.
Have you investigated if the lsp and linter is configurable
replyFrom what I can gather from a cursory glance at the docs, zed uses intelephense and its diagnostics can be disabled. The whole lsp can be disabled. At the risk of sounding like I'm saying "you're holding it wrong", I have to say that this is an OP problem and not a Zed problem. These are sensible defaults that work for almost everyone, in my opinion.
replyThere are no "defaults that work for everyone". Well designed tooling acknowledges that and makes it easy to tune the software to your preference.
reply