fix(gqlorm): use Cedar's pluralization function in graphqlGenerator

[lisa-assistant]

Problem

In packages/gqlorm/src/generator/graphqlGenerator.ts, the #getGraphQLFieldName method generates the GraphQL field name for findMany operations using a naive ${model}s string append:

case 'findMany':
  // TODO: Use Cedar's pluralization function
  // Simple pluralization
  return `${model}s`

This will produce incorrect results for irregular plurals (e.g. Person → Persons instead of People, Datum → Datums instead of Data, Category → Categorys instead of Categories).

Cedar already has a proper pluralization function in packages/utils/src/cedarPluralize.ts (which wraps the pluralize npm package and adds support for PascalCased multi-word identifiers).

Fix

1. Add @cedarjs/utils to packages/gqlorm/package.json dependencies
2. Import pluralize from @cedarjs/utils (or @cedarjs/utils/cedarPluralize) in graphqlGenerator.ts
3. Replace ${model}s with pluralize(model)

import { pluralize } from '@cedarjs/utils'

// ...

case 'findMany':
  return pluralize(model)

Note: cedarPluralize.ts#pluralize already handles PascalCase correctly (e.g. OrderItem → OrderItems, FooBarBaz → FooBarBazs... actually it pluralizes only the last word), so the behavior should be correct for typical Prisma model names.

Files to change

• packages/gqlorm/src/generator/graphqlGenerator.ts — replace naive pluralization
• packages/gqlorm/package.json — add @cedarjs/utils dependency
• packages/gqlorm/src/generator/__tests__/ — add test cases for irregular plurals

[lisa-assistant]

Self-fix confidence: 9/10

The utility function already exists, the fix is 3 lines of code, and the test case is easy to write. The only unknowns are (1) whether @cedarjs/utils is already transitively available to gqlorm via workspace hoisting (would need to add an explicit dep to be safe) and (2) whether any existing tests assert the current naive behavior and need updating.

[lisa-assistant]

Implementation Plan

Goal: Replace the naive ${model}s pluralization in GraphQLGenerator with Cedar's own pluralize() function from @cedarjs/utils, which handles irregular plurals correctly (e.g. Person → People, Category → Categories, etc.).

---

Files to change

1. packages/gqlorm/package.json

Add @cedarjs/utils as a dependency. It's already a workspace package, so:

"dependencies": {
  "@cedarjs/utils": "workspace:*"
}

2. packages/gqlorm/src/generator/graphqlGenerator.ts

Add import near the top:

import { pluralize } from '@cedarjs/utils'

Update #getGraphQLFieldName (around line 142):

Before:

case 'findMany':
  // TODO: Use Cedar's pluralization function
  // Simple pluralization
  return `${model}s`

After:

case 'findMany':
  // Cedar's pluralize() handles irregular plurals (Category → Categories, etc.)
  return pluralize(model)

---

Why this matters

The generated GraphQL field name for findMany must match the name registered in the Cedar GraphQL schema (which also uses pluralize from @cedarjs/utils in SDL generation). A mismatch means gqlorm queries silently fail or return unexpected data. The simple ${model}s suffix fails for:

• Category → Categorys (should be Categories)
• Person → Persons (should be People)
• Mouse → Mouses (should be Mice)

---

Edge cases to consider

1. Model names that are already plural: pluralize('Posts') — verify @cedarjs/utils pluralize is idempotent on already-plural inputs. Looking at packages/utils/src/cedarPluralize.ts, the implementation delegates to the pluralize npm package which handles this correctly.
2. PascalCase model names: pluralize in @cedarjs/utils is documented to handle PascalCased multi-word identifiers by pluralizing only the last word (BlogPost → BlogPosts). This is exactly the right behavior since GraphQL field names for Cedar models follow this convention.
3. Custom plural mappings: @cedarjs/utils exposes addSingularPlural() — if users have registered custom mappings (e.g. for domain-specific words), pluralize() respects them. The naive ${model}s doesn't.

---

Tests

Update tests in packages/gqlorm/src/__tests__/ that assert on the generated query string for findMany operations to expect correct plural forms. Add cases for irregular plurals like Category and Person to prevent regression.