Standardize OrangeHRM hs_hr_config key/value settings handling across runtime and migrations.
npx skills add https://github.com/orangehrm/orangehrm --skill config-orangehrm
Please help me install this Agent Skill. Skill: config Source: https://github.com/orangehrm/orangehrm/tree/main/.agents/skills/config Command: npx skills add https://github.com/orangehrm/orangehrm --skill config-orangehrm
OrangeHRM uses a single key/value settings table (hs_hr_config) for all application-level tunable settings, but inconsistent handling of this table leads to bugs from hardcoded string keys, incorrect type coercion, mixing up runtime and migration access paths, and accidentally storing domain data in the config table instead of proper entities.
Use the config skill to add a new typed getter and setter for the 'auth.password_policy.min_special_chars' setting in ConfigService, and seed its default value of '2' in the next migration script.
High-intent search queries and answers about installing and using this skill.
Use ConfigService and ConfigServiceTrait to add a typed accessor method for runtime access, then seed the default value in a migration script using ConfigHelper. This prevents string key hardcoding errors and ensures proper type coercion for the new setting.
OrangeHRM handles type coercion through ConfigService and ConfigServiceTrait, which provide type-safe accessor patterns for reading and writing config values. This prevents common runtime errors when converting string-stored booleans and numbers from the hs_hr_config table.
To prevent overwriting customized OrangeHRM config settings during upgrade migrations, use ConfigHelper with migration seeding guards. These guards check if a setting already exists before inserting, preserving operator-customized values during re-runs of the migration scripts.
You should store data in the OrangeHRM config table for application-level tunable settings, and use proper entities for per-user or domain data. Storing domain data in config rows causes performance issues from unindexed queries and violates the config vs entity decision framework.
The correct key naming convention for OrangeHRM feature flags uses a dotted namespace format, such as 'auth.password_policy.min_special_chars'. Following this convention ensures consistent access patterns and prevents key collision across different modules and services.
Migration seeding scripts fail when they lack proper guards or use incorrect access paths instead of ConfigHelper. Mixing runtime and migration code paths leads to incorrect type coercion and can accidentally overwrite existing operator-customized settings in the hs_hr_config table.
phoenicisfGenerate and apply UP and DOWN database migrations for EF Core and raw SQL.
nakafaaiDefine and validate Convex database schemas with typed validators and migrations.
orangehrmAlign supported PHP, Composer, database, and CI version configurations across OrangeHRM environments.
thapaliyabikendraModel domain models with entities, relationships, business rules, and permissions.
