I’m having a major issue with Cursor where it keeps changing the case style of my API endpoints. The AI-generated code uses camelCase, but Cursor keeps converting elements to snake_case, which breaks everything.
I’ve tried everything to prevent this:
- Added comments in the API endpoint files explicitly stating not to change the case style.
- Included a README in every directory explaining the case conventions.
- Even added a dedicated README for the API section.
Despite all this, Cursor relentlessly changes the code to snake_case, even when it’s commented out. It’s incredibly frustrating and time-consuming to constantly fix these unintended changes. It feels like Cursor is ignoring the instructions entirely.
To make matters worse, my project is already underway, and I’ve noticed that Cursor seems to recommend or default to snake_case for new projects. While that might be fine for new work, it’s causing chaos in my existing codebase where camelCase is the standard.
Yes, I use Git and version control, so I’m on top of tracking changes, but that doesn’t solve the core issue. What I’m trying to say is that it’s a merry-go-round: Cursor “fixes” one thing and breaks ten others. It doesn’t matter if I specify in the prompt, the README, the project files, the folder structure, or even comments in the code—it just doesn’t listen. It still goes ahead and breaks things.
Has anyone else experienced this? Is there a way to enforce case style rules or prevent Cursor from making these changes? Any help would be greatly appreciated!