chore(orm): add aliased exports for all write operations

[ymc9]

No description provided.

[claude]

Claude finished @ymc9's task —— View job

---

PR Review: Add aliased exports for all write operations

Review Tasks:

• Read and analyze the modified file
• Assess code quality and best practices
• Check for potential bugs or issues
• Evaluate performance considerations
• Review security concerns
• Assess test coverage needs
• Provide comprehensive feedback

Code Review Feedback

Overview

This PR adds AllWriteOperations constant and type exports that are simple aliases of the existing CoreWriteOperations. The changes follow the established pattern used for AllReadOperations.

Code Quality ✅

• Consistent naming: Follows the existing All*Operations naming convention
• Clear documentation: JSDoc comments are consistent with the existing pattern
• Proper TypeScript usage: Uses const assertion and type inference correctly
• Code organization: Added in the logical location alongside similar exports

Implementation Analysis

The changes are minimal and straightforward:

// Added constant alias
export const AllWriteOperations = CoreWriteOperations;

// Added type alias  
export type AllWriteOperations = CoreWriteOperations;

Potential Issues ⚠️

1. Missing export: The new AllWriteOperations exports are not added to packages/orm/src/client/index.ts. Currently, only CoreWriteOperations is exported in the public API. This means the new aliases won't be available to consumers of the package.

2. Semantic question: Unlike AllReadOperations which extends CoreReadOperations with additional operations (findUniqueOrThrow, findFirstOrThrow), AllWriteOperations is just a direct alias. This asymmetry might be confusing:

   • AllReadOperations = [...CoreReadOperations, 'findUniqueOrThrow', 'findFirstOrThrow'] (extends)
   • AllWriteOperations = CoreWriteOperations (alias only)

Performance Considerations ✅

• No performance impact - these are compile-time type definitions and runtime constant references
• Alias approach is more efficient than creating a new array like AllReadOperations

Security Concerns ✅

• No security implications for this change

Test Coverage Recommendations 📋

• Consider adding tests that verify the new exports are available and contain the expected operations
• Test that AllWriteOperations contains the same operations as CoreWriteOperations
• Verify the new exports work correctly in the public API (once added to index.ts)

Suggestions for Improvement

1. Add to public exports: Include AllWriteOperations in packages/orm/src/client/index.ts:8 alongside AllReadOperations
2. Consider consistency: Either document why write operations don't have "orThrow" variants like read operations, or consider if they should be added in the future

Files to Update

• packages/orm/src/client/index.ts - Add AllWriteOperations to the export list

Overall Assessment

This is a clean, well-implemented change that follows established patterns. The main issue is the missing public export, which should be addressed to make the new aliases actually usable by package consumers.

---