Repository navigation
Classes folder
In Pair projects, classes/ is used for application-level custom classes shared across modules.
Typical locations:
APPLICATION_PATH/classes/APPLICATION_PATH/modules/*/classes/
Class loading is handled by Composer autoload (classmap/PSR-4), not by manual preload files.
In the current boilerplate, composer.json includes:
classes/modules/*/classes/
So classes placed there are discovered through Composer autoload.
- Use one class per file.
- Keep file name aligned with class name (for example
Assets.php->Assets). - Use PascalCase for class names.
- Put module-specific classes in that module's
classes/folder. - Put cross-module/shared classes in root
classes/.
Older projects may reference classes/classLoader.php, but this is not part of the current recommended setup.
When navigating form controls, use this page as a shallow index and then move laterally via each page's See also.
Core form docs:
Text and identity inputs:
Choice controls:
Date and time controls:
Numeric and progress controls:
File/media controls:
Maintained by Viames Marino — VM Ingegneria · Professional enquiries
Home · Setup · Configuration
Build with Pair 4
- Generator
- Controllers and responses
- Read models
- ActiveRecord and queries
- Forms and validation
- PairUI.js and HTML fragments
APIs and authentication
- API guide and CRUD
- Middleware and rate limits
- Users, sessions, and ACL
- Passkeys and social login
- Native mobile setup
Integrate and operate
- Integrations
- Runtime extensions and adapter keys
- Cache and cache stores
- Logs and observability
- PWA and push
- Packages and distribution
- Upgrade to v4