Naming inconsistency between frontend and database

Agent & Assistant
1

I have had built 5-6 apps for internal use to date.

All of these have been using agent with default postgresql db + react front end.

I have seen reoccurring issues with agent implementing various forms of naming conventions in different sections of the code - camelCase, snake_case, PascalCase, and whatever else. Are other people seeing this behavior?

How to kill this seemingly straight forward issue with having to include something in each prompt?

1 Like
3

i have an agents.md that specifically says do not use ORM or drizzle, and always use native db field names. It’s crazy what a mess you can get into otherwise between the db field name (snake_case), what the ORM schema calls it (otherCase), and what it gets called in forms.