84ca3dfe42
Move small tasks from wishlist to todo, update npm packages Replace #[Auth] attributes with manual auth checks and code quality rule Remove on_jqhtml_ready lifecycle method from framework Complete ACL system with 100-based role indexing and /dev/acl tester WIP: ACL system implementation with debug instrumentation Convert rsx:check JS linting to RPC socket server Clean up docs and fix $id→$sid in man pages, remove SSR/FPC feature Reorganize wishlists: priority order, mark sublayouts complete, add email Update model_fetch docs: mark MVP complete, fix enum docs, reorganize Comprehensive documentation overhaul: clarity, compression, and critical rules Convert Contacts/Projects CRUD to Model.fetch() and add fetch_or_null() Add JS ORM relationship lazy-loading and fetch array handling Add JS ORM relationship fetching and CRUD documentation Fix ORM hydration and add IDE resolution for Base_* model stubs Rename Json_Tree_Component to JS_Tree_Debug_Component and move to framework Enhance JS ORM infrastructure and add Json_Tree class name badges 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
2.5 KiB
Executable File
2.5 KiB
Executable File
Bundle System
Two-Tier Bundle Architecture
Module Bundles (Rsx_Module_Bundle_Abstract)
- Top-level entry point bundles rendered on pages
- Can scan directories via
includepaths - Auto-discovers Asset Bundles in scanned directories
- Cannot include other Module Bundles (fatal error)
- Built via
rsx:bundle:build
Asset Bundles (Rsx_Asset_Bundle_Abstract)
- Dependency declaration bundles co-located with components
- NO directory scanning - only CDN assets, NPM modules, direct file paths
- Auto-discovered when Module Bundles scan directories containing them
- Never built standalone - metadata consumed by Module Bundles
- Can use
watchdirectories for cache invalidation (e.g., Bootstrap SCSS)
Auto-Discovery Rules:
- Asset Bundles discovered via directory scan cannot have directory paths in
include - If Asset Bundle needs directory scanning, include it explicitly by class name
- Discovery uses
Manifest::php_is_subclass_of()(NOT filename patterns)
Bundle Processor System
Architecture
- Extension-agnostic BundleCompiler: Only handles .js and .css files directly
- Global processor configuration: Processors configured in
config/rsx.phpunderbundle_processors - Processors receive ALL files: Each processor examines all collected files and decides what to process
- No per-bundle processor config: Processors are globally enabled, not per-bundle
How It Works
- BundleCompiler collects ALL files from bundle includes (not just JS/CSS)
- Each configured processor receives the full list of collected files
- Processors decide which files to process based on extension or other criteria
- Processed files replace or augment original files in the bundle
- Final bundle contains JS and CSS files only
Creating a Processor
class MyProcessor extends AbstractBundleProcessor {
public static function get_name(): string { return 'myprocessor'; }
public static function get_extensions(): array { return ['myext']; }
public static function process(string $file_path, array $options = []): ?array {
// Transform file and return result or null to exclude
}
}
Registering Processors
Add to config/rsx.php:
'bundle_processors' => [
\App\RSpade\Processors\MyProcessor::class,
]
SCSS @import Validation
- Non-vendor files: Cannot use @import directives (throws error)
- Vendor files: Files in directories named 'vendor' CAN use @import
- Rationale: @import bypasses bundle dependency management
- Solution: Include dependencies directly in bundle definition