numericals-org
New member
I wanted to share some context around a set of recent PRs where I worked on fixing database-level enum enforcement issues across the codebase. While addressing these issues, I’m now seeing auto-generated documentation checks failing consistently across multiple PRs, and I’d appreciate guidance from the community on the preferred way forward.
The failures suggest that:
What I worked on
Several tables were using TypeScript/Zod enums only, while the database columns were still TEXT. This caused:- Invalid enum values being accepted at the DB level
- Tests expecting DB-level enforcement to fail
- Inconsistent behavior between GraphQL, validation, and database layers
- Converted enum-like TEXT columns to PostgreSQL enums (pgEnum)
- Centralized enum values to avoid drift
- Updated migrations and tests accordingly
- Regenerated auto-docs where required
Related PRs
These PRs are all related to the enum enforcement work:- https://github.com/PalisadoesFoundation/talawa-api/pull/4893
- https://github.com/PalisadoesFoundation/talawa-api/pull/4912
- https://github.com/PalisadoesFoundation/talawa-api/pull/4867
- https://github.com/PalisadoesFoundation/talawa-api/pull/5155
- https://github.com/PalisadoesFoundation/talawa-api/pull/5176
Current issue
Across these PRs, CI is failing on the auto-generated documentation check, even after running pnpm run generate-docs locally and committing the updated files.The failures suggest that:
- Either the docs generator output is sensitive to environment/version differences, or
- The scope of enum changes causes cascading doc updates across multiple areas (Drizzle + GraphQL), making it difficult to keep CI fully in sync across parallel PRs