Create OrangeHRM Doctrine ORM class entities with strict naming conventions.
npx skills add https://github.com/orangehrm/orangehrm --skill entities-orangehrm
Please help me install this Agent Skill. Skill: entities Source: https://github.com/orangehrm/orangehrm/tree/main/.agents/skills/entities Command: npx skills add https://github.com/orangehrm/orangehrm --skill entities-orangehrm
OrangeHRM uses a strict, custom Doctrine ORM setup with specific conventions for entity mapping, naming, and architecture that deviate from default Doctrine patterns. Defining entities without following these rules causes ORM discovery failures, broken relations, legacy compatibility issues, and inconsistent application behavior. This Skill eliminates guesswork by codifying all project-specific entity requirements and common pitfalls.
Follow the entities skill guidelines to define a new Doctrine entity for your OrangeHRM feature with correct table naming, relation mappings, and collection initialization to avoid ORM configuration errors.
High-intent search queries and answers about installing and using this skill.
To create a Doctrine ORM entity in OrangeHRM, use docblock annotation-only mapping, apply the flat namespace, prefix new tables with ohrm_, and initialize ArrayCollections to prevent broken relations.
Doctrine lazy-loading in OrangeHRM fails when relation mappings use incorrect mappedBy or inversedBy values, or when referencedColumnName points to non-standard IDs like emp_number instead of the primary key.
No, PHP 8 attributes cannot be used for ORM mapping in OrangeHRM; the system strictly requires docblock annotation-only mapping to ensure proper entity discovery and avoid configuration errors.
To set up sensitive field encryption in a Doctrine entity, configure an EntityListener to intercept hydration events, applying the project-specific architectural pattern for secure data handling.
The Decorator pattern in OrangeHRM separates entity-adjacent database logic from the Doctrine entity class, allowing custom query and data access methods to operate alongside the mapped ORM structure.
For legacy 4.x table imports in OrangeHRM, prefix database table names with hs_hr_ instead of the standard ohrm_ prefix, and manage legacy ENUM columns using proper reserved name quoting.
orangehrmConfigure Doctrine ORM 2.20 EntityManager and entity discovery in OrangeHRM.
jakubciszakGenerate and apply Doctrine ORM migrations for PostgreSQL schemas.
orangehrmConfigure OrangeHRM REST API v2 Model classes for correct JSON responses.
marquesfelipIdentify and fix SQL injection vulnerabilities in data access layers.
